Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69827ef449db3e64dbe7c6a81db52b47c7c4ccfef6f37edb767ad9161821a392

Tx prefix hash: 7ce0d0b2ca5149e19eb333fecb463d686deba19af9f5f88176bbcfc2d835085f
Tx public key: 76a2f0b95568ceb499f6e9b9c6049af0398f9faf82644a5ac2a0736970e79c61
Timestamp: 1761013608 Timestamp [UCT]: 2025-10-21 02:26:48 Age [y:d:h:m:s]: 00:079:17:16:18
Block: 1394477 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 57074 RingCT/type: yes/0
Extra: 0176a2f0b95568ceb499f6e9b9c6049af0398f9faf82644a5ac2a0736970e79c61021100000003df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: acf0eb42a767a289ee0a1e06e534caa08d8c36f4ea92a54dae61b71b636017f2 0.600000000000 1882748 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": 1394487, "vin": [ { "gen": { "height": 1394477 } } ], "vout": [ { "amount": 600000000, "target": { "key": "acf0eb42a767a289ee0a1e06e534caa08d8c36f4ea92a54dae61b71b636017f2" } } ], "extra": [ 1, 118, 162, 240, 185, 85, 104, 206, 180, 153, 246, 233, 185, 198, 4, 154, 240, 57, 143, 159, 175, 130, 100, 74, 90, 194, 160, 115, 105, 112, 231, 156, 97, 2, 17, 0, 0, 0, 3, 223, 90, 36, 122, 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