Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 078929ff2edac09ddd8c1183cd21af95abfd42e3fee3d7f0d789d26a11b9f1ab

Tx prefix hash: 5b5118797c6e0f613caeddd22f6a64fdbf534f53ef8d2017b14b3d4bcedf927d
Tx public key: 7f1aa285ee6ed46cf8c842f01966100cbc59cebcb01717e8a0d23e66907c167f
Timestamp: 1760685251 Timestamp [UCT]: 2025-10-17 07:14:11 Age [y:d:h:m:s]: 00:034:10:27:58
Block: 1391748 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 24641 RingCT/type: yes/0
Extra: 017f1aa285ee6ed46cf8c842f01966100cbc59cebcb01717e8a0d23e66907c167f0211000000052609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e776126ef930f1a13bf4f7c6a108ae6d17fc10a793785f1e58c9016401f6c5be 0.600000000000 1879995 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": 1391758, "vin": [ { "gen": { "height": 1391748 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e776126ef930f1a13bf4f7c6a108ae6d17fc10a793785f1e58c9016401f6c5be" } } ], "extra": [ 1, 127, 26, 162, 133, 238, 110, 212, 108, 248, 200, 66, 240, 25, 102, 16, 12, 188, 89, 206, 188, 176, 23, 23, 232, 160, 210, 62, 102, 144, 124, 22, 127, 2, 17, 0, 0, 0, 5, 38, 9, 179, 160, 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