Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f069ca0248aa6a1c268af3a019779dd007a32f34b7c23826c2830041bbbf1a3

Tx prefix hash: d4f0cbc85d4b6f863d73ecabfd202ab9fff0a42b7e723bd607cfc9c0e0e307ec
Tx public key: 83f21728a7353c81cdbde3156c6999683aa187057c91e6cd879e8a37052e47b1
Timestamp: 1735646833 Timestamp [UCT]: 2024-12-31 12:07:13 Age [y:d:h:m:s]: 00:324:13:30:19
Block: 1187143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 229474 RingCT/type: yes/0
Extra: 0183f21728a7353c81cdbde3156c6999683aa187057c91e6cd879e8a37052e47b1021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2a16269f95282c376cca97635255704ee225d56b06bf4e488846efd7cb96a90f 0.600000000000 1673630 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": 1187153, "vin": [ { "gen": { "height": 1187143 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2a16269f95282c376cca97635255704ee225d56b06bf4e488846efd7cb96a90f" } } ], "extra": [ 1, 131, 242, 23, 40, 167, 53, 60, 129, 205, 189, 227, 21, 108, 105, 153, 104, 58, 161, 135, 5, 124, 145, 230, 205, 135, 158, 138, 55, 5, 46, 71, 177, 2, 17, 0, 0, 0, 7, 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