Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6fbcd14e66d09572a9de31ee8431e7d20d8e06e6b2804532c908c68f4cd36772

Tx prefix hash: fa49b874b94c7e5f269a977c80387fa83ca6dcabef1072d69e749ef54bb02f62
Tx public key: 757e03873660af8fd65f27d2428856e0b7a4d2d7e722734e375c315bd00853df
Timestamp: 1734152251 Timestamp [UCT]: 2024-12-14 04:57:31 Age [y:d:h:m:s]: 00:105:01:51:44
Block: 1174790 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74873 RingCT/type: yes/0
Extra: 01757e03873660af8fd65f27d2428856e0b7a4d2d7e722734e375c315bd00853df021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 174b8cab73d146f7c9fa8afebdb2fa4a0500e304d35393a4ed1ea04ed57abd27 0.600000000000 1660985 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": 1174800, "vin": [ { "gen": { "height": 1174790 } } ], "vout": [ { "amount": 600000000, "target": { "key": "174b8cab73d146f7c9fa8afebdb2fa4a0500e304d35393a4ed1ea04ed57abd27" } } ], "extra": [ 1, 117, 126, 3, 135, 54, 96, 175, 143, 214, 95, 39, 210, 66, 136, 86, 224, 183, 164, 210, 215, 231, 34, 115, 78, 55, 92, 49, 91, 208, 8, 83, 223, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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