Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1ffbe2da5b63e1eb685136a8a9d5a55690af00745f56d9bf95506481026a37c1

Tx prefix hash: 3e0ca834b3c9c758508d1aa3a42107cde76a0e6f58a489f75c92e3d2e1cc8d4e
Tx public key: 8d620c8eff127168c5da6549e8a25b71e51b5cbbb53675dcd3944383fe3d1a20
Timestamp: 1762998340 Timestamp [UCT]: 2025-11-13 01:45:40 Age [y:d:h:m:s]: 00:008:22:36:20
Block: 1410898 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6407 RingCT/type: yes/0
Extra: 018d620c8eff127168c5da6549e8a25b71e51b5cbbb53675dcd3944383fe3d1a200211000000042609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96ade2d9fd17ac40129cd93e167c100c8a8bca4d5b8d2197cfb2183b7e8519be 0.600000000000 1899353 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": 1410908, "vin": [ { "gen": { "height": 1410898 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96ade2d9fd17ac40129cd93e167c100c8a8bca4d5b8d2197cfb2183b7e8519be" } } ], "extra": [ 1, 141, 98, 12, 142, 255, 18, 113, 104, 197, 218, 101, 73, 232, 162, 91, 113, 229, 27, 92, 187, 181, 54, 117, 220, 211, 148, 67, 131, 254, 61, 26, 32, 2, 17, 0, 0, 0, 4, 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