Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39677a10d9ec85852c5ed080598518cc3367398290c4334025b5763605aeef16

Tx prefix hash: 2bf6662800b8a3fafb5325767126b86898fc9a63cf5ded87b23ff16e8cad1a2f
Tx public key: 465d7e09ec3d7f2f5b3ee37622c24a3428d6d2f865e1d16f5c7833ead9fcc385
Timestamp: 1745625902 Timestamp [UCT]: 2025-04-26 00:05:02 Age [y:d:h:m:s]: 00:282:14:07:51
Block: 1269471 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 199632 RingCT/type: yes/0
Extra: 01465d7e09ec3d7f2f5b3ee37622c24a3428d6d2f865e1d16f5c7833ead9fcc385021100000001dbb571c1000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f5575062f57cb221376f24f9ae9b06ccd0ae51c0c155bc41cf964b7b9d3ef51 0.600000000000 1756710 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": 1269481, "vin": [ { "gen": { "height": 1269471 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f5575062f57cb221376f24f9ae9b06ccd0ae51c0c155bc41cf964b7b9d3ef51" } } ], "extra": [ 1, 70, 93, 126, 9, 236, 61, 127, 47, 91, 62, 227, 118, 34, 194, 74, 52, 40, 214, 210, 248, 101, 225, 209, 111, 92, 120, 51, 234, 217, 252, 195, 133, 2, 17, 0, 0, 0, 1, 219, 181, 113, 193, 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