Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27b01db62f39d8538dda40c5031a834a66d0eff8616438397f3ed6a0b7622627

Tx prefix hash: 2b74756f7866c00e610c786a028c2a3dbb5c09c05ad5066eb4b8ec3a11cb432f
Tx public key: b9f21d3eca5e8ac43072cf67db4a213226fa27cfa75c5b5e59977689d6250aec
Timestamp: 1725082049 Timestamp [UCT]: 2024-08-31 05:27:29 Age [y:d:h:m:s]: 00:221:11:45:11
Block: 1099686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158152 RingCT/type: yes/0
Extra: 01b9f21d3eca5e8ac43072cf67db4a213226fa27cfa75c5b5e59977689d6250aec021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3455b9a581ea748c4301f9a29b4d619de65d4a84526d1bd2abe556ff9489c9f8 0.600000000000 1575651 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": 1099696, "vin": [ { "gen": { "height": 1099686 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3455b9a581ea748c4301f9a29b4d619de65d4a84526d1bd2abe556ff9489c9f8" } } ], "extra": [ 1, 185, 242, 29, 62, 202, 94, 138, 196, 48, 114, 207, 103, 219, 74, 33, 50, 38, 250, 39, 207, 167, 92, 91, 94, 89, 151, 118, 137, 214, 37, 10, 236, 2, 17, 0, 0, 0, 6, 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