Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f8698a90bd403de1d83501ba43ca3f10599a1d59e7c35b86added1c3fc553589

Tx prefix hash: 47a98385a1df4d49a6256922bdff11c13cc4fa6c9be8bfd8323032885bb6cac8
Tx public key: 76293c6ea93d7999aa2ed20716fd8a72b75ed4df560d1aafc3b4a4a22f2ceeb5
Timestamp: 1719577875 Timestamp [UCT]: 2024-06-28 12:31:15 Age [y:d:h:m:s]: 01:135:04:47:16
Block: 1054054 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 355167 RingCT/type: yes/0
Extra: 0176293c6ea93d7999aa2ed20716fd8a72b75ed4df560d1aafc3b4a4a22f2ceeb502110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5262638e1774324958c80cfdbb61368a062c0ba3195c35eafa0d69539c588b0f 0.600000000000 1524413 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": 1054064, "vin": [ { "gen": { "height": 1054054 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5262638e1774324958c80cfdbb61368a062c0ba3195c35eafa0d69539c588b0f" } } ], "extra": [ 1, 118, 41, 60, 110, 169, 61, 121, 153, 170, 46, 210, 7, 22, 253, 138, 114, 183, 94, 212, 223, 86, 13, 26, 175, 195, 180, 164, 162, 47, 44, 238, 181, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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