Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 16254004f72764b4673e07b45f1f3a5610b0d14c3abc0f5deb126f4026b3fec2

Tx prefix hash: 969b3d7c49f89b54b89fdf6a694039ac1c15d8b547247fefd0a743b8bd2d8088
Tx public key: f651c9994f7653cca2ec9ae42d9641e518692c5ae0595a3e4de165913fdf9778
Timestamp: 1729531559 Timestamp [UCT]: 2024-10-21 17:25:59 Age [y:d:h:m:s]: 00:093:01:58:58
Block: 1136540 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 66514 RingCT/type: yes/0
Extra: 01f651c9994f7653cca2ec9ae42d9641e518692c5ae0595a3e4de165913fdf9778021100000004cab32bb9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 39fd1b87c3f9770545b118c68c52bcf9a170bd16619ae6935c87d897466c2cd4 0.600000000000 1619885 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": 1136550, "vin": [ { "gen": { "height": 1136540 } } ], "vout": [ { "amount": 600000000, "target": { "key": "39fd1b87c3f9770545b118c68c52bcf9a170bd16619ae6935c87d897466c2cd4" } } ], "extra": [ 1, 246, 81, 201, 153, 79, 118, 83, 204, 162, 236, 154, 228, 45, 150, 65, 229, 24, 105, 44, 90, 224, 89, 90, 62, 77, 225, 101, 145, 63, 223, 151, 120, 2, 17, 0, 0, 0, 4, 202, 179, 43, 185, 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