Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 450444b44b01b26d7a40991dc41ea524927b1de7904035aa7320f38aac7f4008

Tx prefix hash: 09714f4eb4275b9137e3c4e935dd19b645f967464919d0c082c310282874e9b7
Tx public key: 96c58e7de8a8da52d38d029e627afe2b8796a544ef33a240175d17dfa8cc937a
Timestamp: 1732614079 Timestamp [UCT]: 2024-11-26 09:41:19 Age [y:d:h:m:s]: 00:126:17:32:53
Block: 1162026 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90380 RingCT/type: yes/0
Extra: 0196c58e7de8a8da52d38d029e627afe2b8796a544ef33a240175d17dfa8cc937a0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 11b7adfa4d403c5604bd58bb4b1c2642b37e41bb32962c64ccb205af196d01a1 0.600000000000 1647681 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": 1162036, "vin": [ { "gen": { "height": 1162026 } } ], "vout": [ { "amount": 600000000, "target": { "key": "11b7adfa4d403c5604bd58bb4b1c2642b37e41bb32962c64ccb205af196d01a1" } } ], "extra": [ 1, 150, 197, 142, 125, 232, 168, 218, 82, 211, 141, 2, 158, 98, 122, 254, 43, 135, 150, 165, 68, 239, 51, 162, 64, 23, 93, 23, 223, 168, 204, 147, 122, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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