Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5bd2ee3d8db24f8826f2649893b9917e3d600218fe1dcdddaddd5fe30fcbb1d

Tx prefix hash: ee17d1cb113a8a8f0979733f3b1d6b6c9da3344628083769631028c96a340e50
Tx public key: f7851948e58d5115b3fc3f5f635591ffef5af3f99fba2f2f944fb84ecd619b93
Timestamp: 1714894025 Timestamp [UCT]: 2024-05-05 07:27:05 Age [y:d:h:m:s]: 00:342:22:49:47
Block: 1015235 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245136 RingCT/type: yes/0
Extra: 01f7851948e58d5115b3fc3f5f635591ffef5af3f99fba2f2f944fb84ecd619b9302110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a54d196d7e205b4e23a2057b88b0039c5f9009d9a1c116cdaffc4a70fb22625 0.600000000000 1478542 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": 1015245, "vin": [ { "gen": { "height": 1015235 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a54d196d7e205b4e23a2057b88b0039c5f9009d9a1c116cdaffc4a70fb22625" } } ], "extra": [ 1, 247, 133, 25, 72, 229, 141, 81, 21, 179, 252, 63, 95, 99, 85, 145, 255, 239, 90, 243, 249, 159, 186, 47, 47, 148, 79, 184, 78, 205, 97, 155, 147, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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