Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f43d8a2a57e88b46879d349fd6b724b627bdd157275fd38608cd41ccef4e562

Tx prefix hash: 297a1beb82e3e715101ce398a811bc65bf85a782f7929bbd9b6b9c133c22fd42
Tx public key: f033b113847b1eca0ae1e518467ac18940112b1064d33f4ebd3e4c5ce15d633d
Timestamp: 1732224265 Timestamp [UCT]: 2024-11-21 21:24:25 Age [y:d:h:m:s]: 00:002:04:11:25
Block: 1158803 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 1560 RingCT/type: yes/0
Extra: 01f033b113847b1eca0ae1e518467ac18940112b1064d33f4ebd3e4c5ce15d633d02110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bef48e9a8660d542fd9e705993368916dec356adbe8e78a6f4d92a37de2bcdf8 0.600000000000 1644432 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": 1158813, "vin": [ { "gen": { "height": 1158803 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bef48e9a8660d542fd9e705993368916dec356adbe8e78a6f4d92a37de2bcdf8" } } ], "extra": [ 1, 240, 51, 177, 19, 132, 123, 30, 202, 10, 225, 229, 24, 70, 122, 193, 137, 64, 17, 43, 16, 100, 211, 63, 78, 189, 62, 76, 92, 225, 93, 99, 61, 2, 17, 0, 0, 0, 10, 0, 127, 151, 138, 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