Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b90825bf82949e1bc8e4c0d2e2dd907894b476cf952b67c17d088595a585d893

Tx prefix hash: 1b09ac132a49b0238d072e9455ba3911fd61802f5f1c3286478c7000605b2c9e
Tx public key: d8db881aa03979550b2c0d75200da389b17d9657a220a3936a06415e678d1b5f
Timestamp: 1638817371 Timestamp [UCT]: 2021-12-06 19:02:51 Age [y:d:h:m:s]: 03:330:03:29:15
Block: 389859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1012367 RingCT/type: yes/0
Extra: 01d8db881aa03979550b2c0d75200da389b17d9657a220a3936a06415e678d1b5f0211000000331cab2639000000000000000000

1 output(s) for total of 31.349863998000 dcy

stealth address amount amount idx
00: 16221a4738c83938c9e02c60fd6799f649f9e009470e3d7bc15b0905fc252be5 31.349863998000 785288 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": 389869, "vin": [ { "gen": { "height": 389859 } } ], "vout": [ { "amount": 31349863998, "target": { "key": "16221a4738c83938c9e02c60fd6799f649f9e009470e3d7bc15b0905fc252be5" } } ], "extra": [ 1, 216, 219, 136, 26, 160, 57, 121, 85, 11, 44, 13, 117, 32, 13, 163, 137, 177, 125, 150, 87, 162, 32, 163, 147, 106, 6, 65, 94, 103, 141, 27, 95, 2, 17, 0, 0, 0, 51, 28, 171, 38, 57, 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