Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6d286d4b86a295c118ad030b2cea9a448b7850a0f4f73fe34b663ed83fc4a40

Tx prefix hash: a504e64df413495b2242d7c19e07d9e395d8fb104cc3bc31dabec5dba580b84d
Tx public key: 397850b58ef1f58a4a2b4dc61d099a0d7bf0d66bd1998526dedcc1153065e62c
Timestamp: 1734817818 Timestamp [UCT]: 2024-12-21 21:50:18 Age [y:d:h:m:s]: 00:181:04:04:27
Block: 1180316 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129121 RingCT/type: yes/0
Extra: 01397850b58ef1f58a4a2b4dc61d099a0d7bf0d66bd1998526dedcc1153065e62c02110000000e007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 28903564f9539674604db34d0df9f13af68f9938656142241d2c8b1f2b5efbc2 0.600000000000 1666727 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": 1180326, "vin": [ { "gen": { "height": 1180316 } } ], "vout": [ { "amount": 600000000, "target": { "key": "28903564f9539674604db34d0df9f13af68f9938656142241d2c8b1f2b5efbc2" } } ], "extra": [ 1, 57, 120, 80, 181, 142, 241, 245, 138, 74, 43, 77, 198, 29, 9, 154, 13, 123, 240, 214, 107, 209, 153, 133, 38, 222, 220, 193, 21, 48, 101, 230, 44, 2, 17, 0, 0, 0, 14, 0, 127, 151, 138, 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