Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5fe14707a5cbb041fe8333f2e4c3629144cd40951b9a9f1e79ab865ada44601a

Tx prefix hash: 3c27df7cbdf9a15dacb5a59b9768c4394f11dfeeb170b0f510f811245e7e4e8b
Tx public key: 33c43c8f2594f78a5d3413ab1d0928e86edcbc325ff0fd70327723d1f0638cdc
Timestamp: 1737272805 Timestamp [UCT]: 2025-01-19 07:46:45 Age [y:d:h:m:s]: 00:153:03:55:41
Block: 1200569 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109160 RingCT/type: yes/0
Extra: 0133c43c8f2594f78a5d3413ab1d0928e86edcbc325ff0fd70327723d1f0638cdc021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1d6fc8d843cce3090974f60165db809eb99d5aa98ac0737aab33e7fad70bf0f 0.600000000000 1687214 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": 1200579, "vin": [ { "gen": { "height": 1200569 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1d6fc8d843cce3090974f60165db809eb99d5aa98ac0737aab33e7fad70bf0f" } } ], "extra": [ 1, 51, 196, 60, 143, 37, 148, 247, 138, 93, 52, 19, 171, 29, 9, 40, 232, 110, 220, 188, 50, 95, 240, 253, 112, 50, 119, 35, 209, 240, 99, 140, 220, 2, 17, 0, 0, 0, 5, 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