Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c0990e3d6b734afa8aa1cb5ee17784682127e3432e576d790e204a02f1e223d

Tx prefix hash: bb2e66b274f377fc9f3988fc29c258597fcc83fe1e6e3295380adbb06575c508
Tx public key: 7fc7ff5bfc012d548b2ed3e6d5eb0a4eb6abe10cc5252bd15d680b6c875199b7
Timestamp: 1671090967 Timestamp [UCT]: 2022-12-15 07:56:07 Age [y:d:h:m:s]: 02:142:03:52:50
Block: 652967 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 623311 RingCT/type: yes/0
Extra: 017fc7ff5bfc012d548b2ed3e6d5eb0a4eb6abe10cc5252bd15d680b6c875199b702110000000274b6d784000000000000000000

1 output(s) for total of 4.211620701000 dcy

stealth address amount amount idx
00: 21ad44e60d7322b780d5259d3537d136c27a3feef600852042cbd0e4766fa94a 4.211620701000 1093416 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": 652977, "vin": [ { "gen": { "height": 652967 } } ], "vout": [ { "amount": 4211620701, "target": { "key": "21ad44e60d7322b780d5259d3537d136c27a3feef600852042cbd0e4766fa94a" } } ], "extra": [ 1, 127, 199, 255, 91, 252, 1, 45, 84, 139, 46, 211, 230, 213, 235, 10, 78, 182, 171, 225, 12, 197, 37, 43, 209, 93, 104, 11, 108, 135, 81, 153, 183, 2, 17, 0, 0, 0, 2, 116, 182, 215, 132, 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