Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0dc15fffb0d9b2dc77f73046fec1e44dc391bcd0b4deb38be468c026d5b8ca4

Tx prefix hash: 87e215b1a5c8632cc3e912814dac85d3e68fc03abf42b390f2d6e56659690b83
Tx public key: 4c79abc43c71dbae010028ee937bdd4c7bb1b38aad556ea1e11a30fe56477dbc
Timestamp: 1705614455 Timestamp [UCT]: 2024-01-18 21:47:35 Age [y:d:h:m:s]: 01:078:19:21:44
Block: 938270 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317411 RingCT/type: yes/0
Extra: 014c79abc43c71dbae010028ee937bdd4c7bb1b38aad556ea1e11a30fe56477dbc0211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 90e02786850ca252dcc1245fa2eaa0efb85f4aeb18eb6746e9ab6e31cf785023 0.600000000000 1396340 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": 938280, "vin": [ { "gen": { "height": 938270 } } ], "vout": [ { "amount": 600000000, "target": { "key": "90e02786850ca252dcc1245fa2eaa0efb85f4aeb18eb6746e9ab6e31cf785023" } } ], "extra": [ 1, 76, 121, 171, 196, 60, 113, 219, 174, 1, 0, 40, 238, 147, 123, 221, 76, 123, 177, 179, 138, 173, 85, 110, 161, 225, 26, 48, 254, 86, 71, 125, 188, 2, 17, 0, 0, 0, 3, 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