Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ffa223f75014a6386509d0d7f675bc5dc7e7d02ab7903b335d4db6f38393db92

Tx prefix hash: ce6033d5f7f7499c57d95e00d46783c083a9eab674f3a48e9206b8293c7e5866
Tx public key: 6c95686dc558b3fc0b353d8813d763ec8512f6553f63dda94d892a271be0e682
Timestamp: 1716247199 Timestamp [UCT]: 2024-05-20 23:19:59 Age [y:d:h:m:s]: 00:302:17:38:55
Block: 1026450 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 216383 RingCT/type: yes/0
Extra: 016c95686dc558b3fc0b353d8813d763ec8512f6553f63dda94d892a271be0e6820211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6767572566e09f65bf40539c23286d2342fb63ae3fcf8fc00c1060cb170a2e8 0.600000000000 1493541 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": 1026460, "vin": [ { "gen": { "height": 1026450 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6767572566e09f65bf40539c23286d2342fb63ae3fcf8fc00c1060cb170a2e8" } } ], "extra": [ 1, 108, 149, 104, 109, 197, 88, 179, 252, 11, 53, 61, 136, 19, 215, 99, 236, 133, 18, 246, 85, 63, 99, 221, 169, 77, 137, 42, 39, 27, 224, 230, 130, 2, 17, 0, 0, 0, 2, 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