Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e82bb102c9cff950436e881d120198ac2ef0e0a26533735cd4f9468546689dcc

Tx prefix hash: cced1cd29d080bc88015d097077ba6e478f12a6b4f2da01d2a709aa02c57a3ed
Tx public key: a380c5d5c19ce02c9b6c04f6518ffa7467f0f00a4209c41e1df2e919bffa2cb5
Timestamp: 1760256738 Timestamp [UCT]: 2025-10-12 08:12:18 Age [y:d:h:m:s]: 00:085:16:40:14
Block: 1388182 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 61380 RingCT/type: yes/0
Extra: 01a380c5d5c19ce02c9b6c04f6518ffa7467f0f00a4209c41e1df2e919bffa2cb5021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b33414f97d0b7c46028648c0090d25d7d97a5df93606ba8ee67a058a33bb156c 0.600000000000 1876381 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": 1388192, "vin": [ { "gen": { "height": 1388182 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b33414f97d0b7c46028648c0090d25d7d97a5df93606ba8ee67a058a33bb156c" } } ], "extra": [ 1, 163, 128, 197, 213, 193, 156, 224, 44, 155, 108, 4, 246, 81, 143, 250, 116, 103, 240, 240, 10, 66, 9, 196, 30, 29, 242, 233, 25, 191, 250, 44, 181, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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