Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db34866acd7b7fb7d488633b7b339a4fbeb637ab7d2637c948660ad3cc42d7d4

Tx prefix hash: afdd25abb2d973cc0083570cb2eb54249313690aa891f7393484c2ccd0b8b0f2
Tx public key: 6716ee99dd2d253b7647a48b7caa40d3108c6f414b92e583732ac07a6df381f0
Timestamp: 1681230098 Timestamp [UCT]: 2023-04-11 16:21:38 Age [y:d:h:m:s]: 01:364:11:11:31
Block: 736378 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 521773 RingCT/type: yes/0
Extra: 016716ee99dd2d253b7647a48b7caa40d3108c6f414b92e583732ac07a6df381f0021100000002b3164c24000000000000000000

1 output(s) for total of 2.228816037000 dcy

stealth address amount amount idx
00: 9b2e6d7ec8b9380ecd3bb9b5b8b6f9ae5a2801c22d761f2fbdb13da989a9a6f3 2.228816037000 1182805 of 0

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": 736388, "vin": [ { "gen": { "height": 736378 } } ], "vout": [ { "amount": 2228816037, "target": { "key": "9b2e6d7ec8b9380ecd3bb9b5b8b6f9ae5a2801c22d761f2fbdb13da989a9a6f3" } } ], "extra": [ 1, 103, 22, 238, 153, 221, 45, 37, 59, 118, 71, 164, 139, 124, 170, 64, 211, 16, 140, 111, 65, 75, 146, 229, 131, 115, 42, 192, 122, 109, 243, 129, 240, 2, 17, 0, 0, 0, 2, 179, 22, 76, 36, 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