Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 25e96ed38a70750429df93ea136ef8a4458201c9ce428e4bd979dbdd3a1b8d28

Tx prefix hash: b7f749a4117c9c3617e3a834bca41b088fb8b8aced892af0a1a5b4ce539ff0df
Tx public key: 54f3e1c4c56e0df1f9a0b6e4d5e9e1571aa56291b8f2182bc24f1eb128a37ad6
Timestamp: 1737178001 Timestamp [UCT]: 2025-01-18 05:26:41 Age [y:d:h:m:s]: 00:058:05:50:18
Block: 1199820 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 41419 RingCT/type: yes/0
Extra: 0154f3e1c4c56e0df1f9a0b6e4d5e9e1571aa56291b8f2182bc24f1eb128a37ad6021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 686efc0259bf6c87397c43ac5e8573371390f637a48315701eaae7f2937894b8 0.600000000000 1686453 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": 1199830, "vin": [ { "gen": { "height": 1199820 } } ], "vout": [ { "amount": 600000000, "target": { "key": "686efc0259bf6c87397c43ac5e8573371390f637a48315701eaae7f2937894b8" } } ], "extra": [ 1, 84, 243, 225, 196, 197, 110, 13, 241, 249, 160, 182, 228, 213, 233, 225, 87, 26, 165, 98, 145, 184, 242, 24, 43, 194, 79, 30, 177, 40, 163, 122, 214, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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