Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 75b45fb678d1d482c314244c32ba5b843027be73ac449b390f4d0cbcb6ae61b7

Tx prefix hash: 68f0f39ad7bf4fc0bad011c374ee0ae114e5c4045edc1c61fdf33807cd6a186b
Tx public key: 2b8edc003905a48483c714229fc5cda525a15e868a6de1e73e62d9550726d6c1
Timestamp: 1729116414 Timestamp [UCT]: 2024-10-16 22:06:54 Age [y:d:h:m:s]: 00:038:06:18:56
Block: 1133137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 27307 RingCT/type: yes/0
Extra: 012b8edc003905a48483c714229fc5cda525a15e868a6de1e73e62d9550726d6c10211000000023cd0fc06000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ba783c278d8be4cbdd42acc18f6ed38c8ae2f184fa744e9c60403465567d5e98 0.600000000000 1616206 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": 1133147, "vin": [ { "gen": { "height": 1133137 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba783c278d8be4cbdd42acc18f6ed38c8ae2f184fa744e9c60403465567d5e98" } } ], "extra": [ 1, 43, 142, 220, 0, 57, 5, 164, 132, 131, 199, 20, 34, 159, 197, 205, 165, 37, 161, 94, 134, 138, 109, 225, 231, 62, 98, 217, 85, 7, 38, 214, 193, 2, 17, 0, 0, 0, 2, 60, 208, 252, 6, 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