Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9a359b0a75403790a945f6cdc58602c02414a5d1e916a26c88db6ea7477074e

Tx prefix hash: bfbf7da222172603406ae3c5a87479ff94fb05402f5497facf70273479f7107d
Tx public key: 526f6e53ed1dbd23fc4b62498fcd242d04bf25a2cc59503aa2fab0b177fcbf4c
Timestamp: 1726217373 Timestamp [UCT]: 2024-09-13 08:49:33 Age [y:d:h:m:s]: 00:121:01:52:43
Block: 1109097 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86594 RingCT/type: yes/0
Extra: 01526f6e53ed1dbd23fc4b62498fcd242d04bf25a2cc59503aa2fab0b177fcbf4c021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7369e5c6ccf70685ef9075f0331e9fb99bdd0e1cb6842d12e4f578cddf37234 0.600000000000 1587226 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": 1109107, "vin": [ { "gen": { "height": 1109097 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7369e5c6ccf70685ef9075f0331e9fb99bdd0e1cb6842d12e4f578cddf37234" } } ], "extra": [ 1, 82, 111, 110, 83, 237, 29, 189, 35, 252, 75, 98, 73, 143, 205, 36, 45, 4, 191, 37, 162, 204, 89, 80, 58, 162, 250, 176, 177, 119, 252, 191, 76, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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