Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b76fe76e64a98075b7fdd541de4a1988da6e11c1e7184f3128da716677e7525d

Tx prefix hash: 1bc17d219219c16ae5a73e81adba05878d2c970857b258eef25655c45adfe0ab
Tx public key: 8aafd41329afd274e9eb5a5080a9ea36a28a9ad3216d3e3388fbc45b9bcfd998
Timestamp: 1765121900 Timestamp [UCT]: 2025-12-07 15:38:20 Age [y:d:h:m:s]: 00:015:14:52:55
Block: 1428499 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 11185 RingCT/type: yes/0
Extra: 018aafd41329afd274e9eb5a5080a9ea36a28a9ad3216d3e3388fbc45b9bcfd9980211000000047b1e51ac000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 01ebd83938cf95d34a6daa886c9740e4a66a4e133bcb15b5ef8450ec466b3acd 0.600000000000 1917216 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": 1428509, "vin": [ { "gen": { "height": 1428499 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01ebd83938cf95d34a6daa886c9740e4a66a4e133bcb15b5ef8450ec466b3acd" } } ], "extra": [ 1, 138, 175, 212, 19, 41, 175, 210, 116, 233, 235, 90, 80, 128, 169, 234, 54, 162, 138, 154, 211, 33, 109, 62, 51, 136, 251, 196, 91, 155, 207, 217, 152, 2, 17, 0, 0, 0, 4, 123, 30, 81, 172, 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