Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 863edee3addbc1c2c32a6ffab9fc9ce36112d86d7db935ac3557c7898b018635

Tx prefix hash: 2c243973cc54b1e1ca472e1770430d29e7a1b2cd8599464b70d2f71baa0ba8c2
Tx public key: 95c4facb2dabfbf99a8bf2cc476bf18c04e904c570c2f3128e496327b88ae240
Timestamp: 1713362963 Timestamp [UCT]: 2024-04-17 14:09:23 Age [y:d:h:m:s]: 00:156:22:12:50
Block: 1002524 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112420 RingCT/type: yes/0
Extra: 0195c4facb2dabfbf99a8bf2cc476bf18c04e904c570c2f3128e496327b88ae24002110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a7ca082cd2e063ce08c3e52a871d00a9f30a793232043e9963e4f35ff9315cc 0.600000000000 1463040 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": 1002534, "vin": [ { "gen": { "height": 1002524 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a7ca082cd2e063ce08c3e52a871d00a9f30a793232043e9963e4f35ff9315cc" } } ], "extra": [ 1, 149, 196, 250, 203, 45, 171, 251, 249, 154, 139, 242, 204, 71, 107, 241, 140, 4, 233, 4, 197, 112, 194, 243, 18, 142, 73, 99, 39, 184, 138, 226, 64, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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