Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7d918f775a27a67c89075e6683fef76ca09331a57b8277243a18df3a2e89289e

Tx prefix hash: 5e096fd7f7a9ca7d4694c326926510d24e9b241979c1b18789f64670216c88ab
Tx public key: 8d4bcba413e049dfbe1202ab15c97506d6e5557d1548881b5eaf3c4acd8467cd
Timestamp: 1751795364 Timestamp [UCT]: 2025-07-06 09:49:24 Age [y:d:h:m:s]: 00:137:23:47:03
Block: 1319852 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97005 RingCT/type: yes/0
Extra: 018d4bcba413e049dfbe1202ab15c97506d6e5557d1548881b5eaf3c4acd8467cd02110000000443846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 40e76a29881a0185153e2165c079362077c9d7e2d2f66c5384e56b9b5c9febe0 0.600000000000 1807545 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": 1319862, "vin": [ { "gen": { "height": 1319852 } } ], "vout": [ { "amount": 600000000, "target": { "key": "40e76a29881a0185153e2165c079362077c9d7e2d2f66c5384e56b9b5c9febe0" } } ], "extra": [ 1, 141, 75, 203, 164, 19, 224, 73, 223, 190, 18, 2, 171, 21, 201, 117, 6, 214, 229, 85, 125, 21, 72, 136, 27, 94, 175, 60, 74, 205, 132, 103, 205, 2, 17, 0, 0, 0, 4, 67, 132, 109, 102, 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