Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ccd40f0917499a0d639c99af625dc8c73d0e73035f023ee0e42f2bd363706210

Tx prefix hash: 8c3f8670b522f4f826fa4f865f273e5b56fcf3f469fbec87d68ff274c7847130
Tx public key: c33e70f1fea75846692f2089bb597a96781aa2e333a473c4dcbd4f1fb60432ff
Timestamp: 1704992832 Timestamp [UCT]: 2024-01-11 17:07:12 Age [y:d:h:m:s]: 01:297:09:13:24
Block: 933130 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 471349 RingCT/type: yes/0
Extra: 01c33e70f1fea75846692f2089bb597a96781aa2e333a473c4dcbd4f1fb60432ff0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d9830ab21ab2260d2b9d0a46346c61865bba3231e51b15a0a1960f1dafbfa4a0 0.600000000000 1391086 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": 933140, "vin": [ { "gen": { "height": 933130 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d9830ab21ab2260d2b9d0a46346c61865bba3231e51b15a0a1960f1dafbfa4a0" } } ], "extra": [ 1, 195, 62, 112, 241, 254, 167, 88, 70, 105, 47, 32, 137, 187, 89, 122, 150, 120, 26, 162, 227, 51, 164, 115, 196, 220, 189, 79, 31, 182, 4, 50, 255, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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