Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 36b9a6499a25c5f546ce150d74145f538a22168d5469a92a830f9a1aab607fc0

Tx prefix hash: 3e88af54a47b3757afd1b10d64bc14ed48d3c35241cf8456000fe565fff8e552
Tx public key: edcb2fdcc5de70cf264d589d7d77a7dbaad13bc50fe9a258b86f6f79f3a01db6
Timestamp: 1682346367 Timestamp [UCT]: 2023-04-24 14:26:07 Age [y:d:h:m:s]: 01:284:17:24:08
Block: 745634 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 464721 RingCT/type: yes/0
Extra: 01edcb2fdcc5de70cf264d589d7d77a7dbaad13bc50fe9a258b86f6f79f3a01db6021100000003e7ace25d000000000000000000

1 output(s) for total of 2.076850523000 dcy

stealth address amount amount idx
00: 3e8118aff1e7130cd43a6dc2a8d8a13917101badadfcf4b6938b4cecc8d3aba1 2.076850523000 1193103 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 745644, "vin": [ { "gen": { "height": 745634 } } ], "vout": [ { "amount": 2076850523, "target": { "key": "3e8118aff1e7130cd43a6dc2a8d8a13917101badadfcf4b6938b4cecc8d3aba1" } } ], "extra": [ 1, 237, 203, 47, 220, 197, 222, 112, 207, 38, 77, 88, 157, 125, 119, 167, 219, 170, 209, 59, 197, 15, 233, 162, 88, 184, 111, 111, 121, 243, 160, 29, 182, 2, 17, 0, 0, 0, 3, 231, 172, 226, 93, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8