Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd6700533a36824664b5d1899862699580091755f6a2f600723e93fa9e67e384

Tx prefix hash: d313cd503595c89ffe15d0f9534752232617d447fdc403492d334dadbfc60e3d
Tx public key: 2f4d66e77af2743544dcb93df3bb1f273cf6d945fb9c12eded8cd095f583b5c3
Timestamp: 1702114931 Timestamp [UCT]: 2023-12-09 09:42:11 Age [y:d:h:m:s]: 01:041:19:24:00
Block: 909269 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291216 RingCT/type: yes/0
Extra: 012f4d66e77af2743544dcb93df3bb1f273cf6d945fb9c12eded8cd095f583b5c3021100000001faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 27235ca99b21f3ec569f2365c06b7bd23054cd6c1aa9731712745ed07b6fe6a8 0.600000000000 1366340 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": 909279, "vin": [ { "gen": { "height": 909269 } } ], "vout": [ { "amount": 600000000, "target": { "key": "27235ca99b21f3ec569f2365c06b7bd23054cd6c1aa9731712745ed07b6fe6a8" } } ], "extra": [ 1, 47, 77, 102, 231, 122, 242, 116, 53, 68, 220, 185, 61, 243, 187, 31, 39, 60, 246, 217, 69, 251, 156, 18, 237, 237, 140, 208, 149, 245, 131, 181, 195, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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