Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c5eedbf1aec21d9fadc15e175503f0df67b5869f8c43c3d45c932726f2f006a

Tx prefix hash: 2c65cbad2b11617b132f01019f952810c45993b3365a215ca7b5dcf82e630860
Tx public key: 3f5a1ea6f5e9ba1baf709cc186ca1f7f2cdcecf26e69c8c6b2f8eaaa32cefb6b
Timestamp: 1715965719 Timestamp [UCT]: 2024-05-17 17:08:39 Age [y:d:h:m:s]: 00:181:13:12:37
Block: 1024114 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129937 RingCT/type: yes/0
Extra: 013f5a1ea6f5e9ba1baf709cc186ca1f7f2cdcecf26e69c8c6b2f8eaaa32cefb6b02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 929728bcf4ac046c99c87db1a188237b532e87187aee0b0a7a11dc32f5fbc0c0 0.600000000000 1489605 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": 1024124, "vin": [ { "gen": { "height": 1024114 } } ], "vout": [ { "amount": 600000000, "target": { "key": "929728bcf4ac046c99c87db1a188237b532e87187aee0b0a7a11dc32f5fbc0c0" } } ], "extra": [ 1, 63, 90, 30, 166, 245, 233, 186, 27, 175, 112, 156, 193, 134, 202, 31, 127, 44, 220, 236, 242, 110, 105, 200, 198, 178, 248, 234, 170, 50, 206, 251, 107, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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