Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa2fb81de1428ff9fc4f87bf027acbd9ac7aa5fc0e1260d923f37ba038c62643

Tx prefix hash: 2e376e4dc4af607ec4a6c79bca7612239de2c70f076057b17ea4382e17dff3c4
Tx public key: 4c4dbdf2cd7b0e552618d1bf520bfb1a6e956cc10fecb9abc6f2c2886f3feed6
Timestamp: 1719578526 Timestamp [UCT]: 2024-06-28 12:42:06 Age [y:d:h:m:s]: 00:319:13:48:31
Block: 1054058 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228382 RingCT/type: yes/0
Extra: 014c4dbdf2cd7b0e552618d1bf520bfb1a6e956cc10fecb9abc6f2c2886f3feed60211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 471c4b0926506bd4198c5af9aa4ab98d9e77cb4eaf103791ac55116732c07644 0.600000000000 1524417 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": 1054068, "vin": [ { "gen": { "height": 1054058 } } ], "vout": [ { "amount": 600000000, "target": { "key": "471c4b0926506bd4198c5af9aa4ab98d9e77cb4eaf103791ac55116732c07644" } } ], "extra": [ 1, 76, 77, 189, 242, 205, 123, 14, 85, 38, 24, 209, 191, 82, 11, 251, 26, 110, 149, 108, 193, 15, 236, 185, 171, 198, 242, 194, 136, 111, 63, 238, 214, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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