Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b56ea7d2b8ac2b37fdd52522e5328cb419e266175845bef912f990c89e3c631c

Tx prefix hash: 82933b9a1b5ee42293b78ea40661b535f1547b5a40eb5d0a1faeef14e0e8b27f
Tx public key: 073e6d8471cf4d1b41ea447995aa13c6991a204de51ed3071f4e527a77dfa1a9
Timestamp: 1712077082 Timestamp [UCT]: 2024-04-02 16:58:02 Age [y:d:h:m:s]: 00:281:12:37:10
Block: 991840 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201554 RingCT/type: yes/0
Extra: 01073e6d8471cf4d1b41ea447995aa13c6991a204de51ed3071f4e527a77dfa1a90211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: df08b4ea26ddf98a6eb915bd5ff78deb9ee8d0bad0487727270bc7615702d1e8 0.600000000000 1452176 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": 991850, "vin": [ { "gen": { "height": 991840 } } ], "vout": [ { "amount": 600000000, "target": { "key": "df08b4ea26ddf98a6eb915bd5ff78deb9ee8d0bad0487727270bc7615702d1e8" } } ], "extra": [ 1, 7, 62, 109, 132, 113, 207, 77, 27, 65, 234, 68, 121, 149, 170, 19, 198, 153, 26, 32, 77, 229, 30, 211, 7, 31, 78, 82, 122, 119, 223, 161, 169, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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