Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2f9abe25b5a36d85a4a062a0b908b5677f65af8b66376391b34fac6f6154049

Tx prefix hash: c0072bf77f737fd53f66fab8f906753605be5361b0bea6dd9dc44f5dbb46fc1c
Tx public key: 9db3f16da2c0d34859dfc09837d791580635b8eda0c31d7fc9733fdbcb1a7d48
Timestamp: 1715538632 Timestamp [UCT]: 2024-05-12 18:30:32 Age [y:d:h:m:s]: 01:029:10:04:44
Block: 1020595 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 281926 RingCT/type: yes/0
Extra: 019db3f16da2c0d34859dfc09837d791580635b8eda0c31d7fc9733fdbcb1a7d48021100000001679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b942428f20195c72ab06649612b754ea7a2cde9e7a2de80f0e4a552875301359 0.600000000000 1484676 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": 1020605, "vin": [ { "gen": { "height": 1020595 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b942428f20195c72ab06649612b754ea7a2cde9e7a2de80f0e4a552875301359" } } ], "extra": [ 1, 157, 179, 241, 109, 162, 192, 211, 72, 89, 223, 192, 152, 55, 215, 145, 88, 6, 53, 184, 237, 160, 195, 29, 127, 201, 115, 63, 219, 203, 26, 125, 72, 2, 17, 0, 0, 0, 1, 103, 154, 138, 129, 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