Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0feb974de185edd9b48acb231407be78c1b7c805096761a4f4e7a3ff27811b0

Tx prefix hash: 13ff8536c311bff7384f31f3fbe0393aa690a6097b34ba3236ddc102e9f0b1a7
Tx public key: 082f7e148d14d3707e168b0f855fa7ddf59e4f68b11d1e98f8ee7f8e47396237
Timestamp: 1670547932 Timestamp [UCT]: 2022-12-09 01:05:32 Age [y:d:h:m:s]: 02:122:04:28:59
Block: 648457 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 609029 RingCT/type: yes/0
Extra: 01082f7e148d14d3707e168b0f855fa7ddf59e4f68b11d1e98f8ee7f8e47396237021100000001272bcc39000000000000000000

1 output(s) for total of 4.359059133000 dcy

stealth address amount amount idx
00: f49140c7fc2ce1f13896da6aeafe33b180f4dd3caef991bdb345d678367975db 4.359059133000 1088798 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": 648467, "vin": [ { "gen": { "height": 648457 } } ], "vout": [ { "amount": 4359059133, "target": { "key": "f49140c7fc2ce1f13896da6aeafe33b180f4dd3caef991bdb345d678367975db" } } ], "extra": [ 1, 8, 47, 126, 20, 141, 20, 211, 112, 126, 22, 139, 15, 133, 95, 167, 221, 245, 158, 79, 104, 177, 29, 30, 152, 248, 238, 127, 142, 71, 57, 98, 55, 2, 17, 0, 0, 0, 1, 39, 43, 204, 57, 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