Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cade856b0abf16005438f6af6d3d37d3031892b9be28e3784836a264aaab992f

Tx prefix hash: f60bcdf5f29c24489404ae6ab10be62ff03f0aa94392d689f2bba4d976bd4193
Tx public key: bcd1fad6d7463450448586da679f1eb8c349cd13c0c5a438b49c1a0257a3c892
Timestamp: 1708937137 Timestamp [UCT]: 2024-02-26 08:45:37 Age [y:d:h:m:s]: 01:032:01:45:55
Block: 965843 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283931 RingCT/type: yes/0
Extra: 01bcd1fad6d7463450448586da679f1eb8c349cd13c0c5a438b49c1a0257a3c8920211000000010546d7d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d639c9c3fa3d777a6b985e955fd7f36841b1e1c93eb6fa0aee7afcef0ba2f2cf 0.600000000000 1425598 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": 965853, "vin": [ { "gen": { "height": 965843 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d639c9c3fa3d777a6b985e955fd7f36841b1e1c93eb6fa0aee7afcef0ba2f2cf" } } ], "extra": [ 1, 188, 209, 250, 214, 215, 70, 52, 80, 68, 133, 134, 218, 103, 159, 30, 184, 195, 73, 205, 19, 192, 197, 164, 56, 180, 156, 26, 2, 87, 163, 200, 146, 2, 17, 0, 0, 0, 1, 5, 70, 215, 208, 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