Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a23c396b52ee7373aa7e89d231d85a4f350b2146b1d343d1a2b2c2384c23814b

Tx prefix hash: 4c5a671c49f6e3e1ef586c56f5d0c9e6c75581139d000f5340f590a7fd9611f7
Tx public key: 2a72cb05202d4a64ac36e50b3fd040e8bf78b39851e7f8d7eff5b63c8a4acbb0
Timestamp: 1761380867 Timestamp [UCT]: 2025-10-25 08:27:47 Age [y:d:h:m:s]: 00:098:09:23:34
Block: 1397527 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70243 RingCT/type: yes/0
Extra: 012a72cb05202d4a64ac36e50b3fd040e8bf78b39851e7f8d7eff5b63c8a4acbb00211000000035dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d4829db63c4438f76eec2402ce9fffc0dc9572c4edb1704dd7ffdd259ee7fc2e 0.600000000000 1885818 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": 1397537, "vin": [ { "gen": { "height": 1397527 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d4829db63c4438f76eec2402ce9fffc0dc9572c4edb1704dd7ffdd259ee7fc2e" } } ], "extra": [ 1, 42, 114, 203, 5, 32, 45, 74, 100, 172, 54, 229, 11, 63, 208, 64, 232, 191, 120, 179, 152, 81, 231, 248, 215, 239, 245, 182, 60, 138, 74, 203, 176, 2, 17, 0, 0, 0, 3, 93, 251, 190, 42, 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