Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6580469e6da51b4ee4f86517b2c2808c2e71abb6658c5d898059849038255a2b

Tx prefix hash: 3d49a67a854833bcab202b2fc8f5a29c94360917fdd960573c21477d96218bb3
Tx public key: 94dc44fdab93d6f0aa00c1d1530c4b2bb84f2432a155e68150937d6cc7fd1a22
Timestamp: 1719203941 Timestamp [UCT]: 2024-06-24 04:39:01 Age [y:d:h:m:s]: 01:137:08:17:57
Block: 1050948 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356714 RingCT/type: yes/0
Extra: 0194dc44fdab93d6f0aa00c1d1530c4b2bb84f2432a155e68150937d6cc7fd1a2202110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 037776f91322ed92d00bea82f7d23c1b221aed51210c0637a4bc5f16328b5510 0.600000000000 1521125 of 15

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": 1050958, "vin": [ { "gen": { "height": 1050948 } } ], "vout": [ { "amount": 600000000, "target": { "key": "037776f91322ed92d00bea82f7d23c1b221aed51210c0637a4bc5f16328b5510" } } ], "extra": [ 1, 148, 220, 68, 253, 171, 147, 214, 240, 170, 0, 193, 209, 83, 12, 75, 43, 184, 79, 36, 50, 161, 85, 230, 129, 80, 147, 125, 108, 199, 253, 26, 34, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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