Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cce9ad8dbca3470abb1c0c1bd0b2f5124ece585f74206180ffb5df70ddd66d2b

Tx prefix hash: f7e15d6ce53a707345aedc3cb61d9fc02cb97da6ebaafd3840a6fd2c244f87f1
Tx public key: f39eebc0f4e9b66d57cc7866ca489247e9b56d5f27d23875e968a33b64ea754b
Timestamp: 1581238216 Timestamp [UCT]: 2020-02-09 08:50:16 Age [y:d:h:m:s]: 04:283:13:29:13
Block: 61143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1094835 RingCT/type: yes/0
Extra: 01f39eebc0f4e9b66d57cc7866ca489247e9b56d5f27d23875e968a33b64ea754b02110000000e4ac5aa02000000000000000000

1 output(s) for total of 384.953857567000 dcy

stealth address amount amount idx
00: f045a726868fa221f9871ea4ccb31eccfb982f5d8279c9ac7fb974a24c72763b 384.953857567000 112672 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": 61153, "vin": [ { "gen": { "height": 61143 } } ], "vout": [ { "amount": 384953857567, "target": { "key": "f045a726868fa221f9871ea4ccb31eccfb982f5d8279c9ac7fb974a24c72763b" } } ], "extra": [ 1, 243, 158, 235, 192, 244, 233, 182, 109, 87, 204, 120, 102, 202, 72, 146, 71, 233, 181, 109, 95, 39, 210, 56, 117, 233, 104, 163, 59, 100, 234, 117, 75, 2, 17, 0, 0, 0, 14, 74, 197, 170, 2, 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