Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82d24a650fc3060bbac2dc9d2352fa07c44b77887d78f19d0b4fe6a0cd24c931

Tx prefix hash: 7ab379b7e93212d4a27de73161431588c4a128966dd7ddf16730a236a6a9a445
Tx public key: cc45f455296e7ff1ee9a000f19b7b8c0dfc619de05138f825330f605791482f2
Timestamp: 1725072423 Timestamp [UCT]: 2024-08-31 02:47:03 Age [y:d:h:m:s]: 00:235:01:37:12
Block: 1099602 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167867 RingCT/type: yes/0
Extra: 01cc45f455296e7ff1ee9a000f19b7b8c0dfc619de05138f825330f605791482f202110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b9b48a0fffb55ea143e724f6d3bbdaf5f79498cf655f68a9f56b4fbbb8942a0 0.600000000000 1575567 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": 1099612, "vin": [ { "gen": { "height": 1099602 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b9b48a0fffb55ea143e724f6d3bbdaf5f79498cf655f68a9f56b4fbbb8942a0" } } ], "extra": [ 1, 204, 69, 244, 85, 41, 110, 127, 241, 238, 154, 0, 15, 25, 183, 184, 192, 223, 198, 25, 222, 5, 19, 143, 130, 83, 48, 246, 5, 121, 20, 130, 242, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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