Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0395d45892eef50678d3a653bdae5f645c16a1ae21eafe15aec44f95a1d8fa49

Tx prefix hash: 89214930eedc866f908442386d65ac91f668b75bc821755086db4fa3e819ba9a
Tx public key: 11d6b6560b763c5d336a9c29b397b43f6400b5a3d51abdbc6605eae860f777fa
Timestamp: 1761418716 Timestamp [UCT]: 2025-10-25 18:58:36 Age [y:d:h:m:s]: 00:026:09:06:28
Block: 1397824 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 18868 RingCT/type: yes/0
Extra: 0111d6b6560b763c5d336a9c29b397b43f6400b5a3d51abdbc6605eae860f777fa021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0db0917a5c205b0a8848db8191d6bac3d58078e61af6b4f1e5347357ceae8739 0.600000000000 1886115 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": 1397834, "vin": [ { "gen": { "height": 1397824 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0db0917a5c205b0a8848db8191d6bac3d58078e61af6b4f1e5347357ceae8739" } } ], "extra": [ 1, 17, 214, 182, 86, 11, 118, 60, 93, 51, 106, 156, 41, 179, 151, 180, 63, 100, 0, 181, 163, 213, 26, 189, 188, 102, 5, 234, 232, 96, 247, 119, 250, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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