Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ddc45e91b7796fbf31cb5525bfbb7fe060da2161f33dab79e29c1de99cab7c69

Tx prefix hash: 1a42c9403ead5bb45f83b1b37940d791bf081508f5d9a79197eea8390a0a5beb
Tx public key: 09d8b0a8573175aff93c39fb8ed52e76611f64dcafeb2f4403ecdb01e6a7d2d3
Timestamp: 1682618164 Timestamp [UCT]: 2023-04-27 17:56:04 Age [y:d:h:m:s]: 01:260:01:06:54
Block: 747889 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 447327 RingCT/type: yes/0
Extra: 0109d8b0a8573175aff93c39fb8ed52e76611f64dcafeb2f4403ecdb01e6a7d2d3021100000006b3164c24000000000000000000

1 output(s) for total of 2.041425267000 dcy

stealth address amount amount idx
00: 964927636f500d726df0c47ce277e711966df63cb71eb01904ca555b4126097c 2.041425267000 1195654 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": 747899, "vin": [ { "gen": { "height": 747889 } } ], "vout": [ { "amount": 2041425267, "target": { "key": "964927636f500d726df0c47ce277e711966df63cb71eb01904ca555b4126097c" } } ], "extra": [ 1, 9, 216, 176, 168, 87, 49, 117, 175, 249, 60, 57, 251, 142, 213, 46, 118, 97, 31, 100, 220, 175, 235, 47, 68, 3, 236, 219, 1, 230, 167, 210, 211, 2, 17, 0, 0, 0, 6, 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