Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cc4d749ed041a565eb5bba7bee9c2b28de3242fdb56b4bcc83798a1f437852e3

Tx prefix hash: 7b00041ac67aa35b67035e82a25e1c4c22284f4f9121f0f8c812f13566f717a7
Tx public key: dbdab0c920b54bbad3713a5f7450dc9c6e76c71ddb7e49a20adc77ffa7919546
Timestamp: 1702827009 Timestamp [UCT]: 2023-12-17 15:30:09 Age [y:d:h:m:s]: 01:121:11:28:07
Block: 915179 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 347953 RingCT/type: yes/0
Extra: 01dbdab0c920b54bbad3713a5f7450dc9c6e76c71ddb7e49a20adc77ffa7919546021100000003faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8ffac0230399ccd2b9806dfdc414073031b5cd1113b91faff5aec82c0108689c 0.600000000000 1372565 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": 915189, "vin": [ { "gen": { "height": 915179 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8ffac0230399ccd2b9806dfdc414073031b5cd1113b91faff5aec82c0108689c" } } ], "extra": [ 1, 219, 218, 176, 201, 32, 181, 75, 186, 211, 113, 58, 95, 116, 80, 220, 156, 110, 118, 199, 29, 219, 126, 73, 162, 10, 220, 119, 255, 167, 145, 149, 70, 2, 17, 0, 0, 0, 3, 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