Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e007b34d65a100642cc081eec28a1ef7a3bf83a0778557b3a2fa9b9bcf0e65dd

Tx prefix hash: 0636dbb320867cef45178391a7bdfeac3e5fdfab00357b872f61e1661ac043de
Tx public key: bcd2b32ca051b6326152c0062e0d2e2025d50db78cae389b2e8d0a3ad72cb883
Timestamp: 1752158722 Timestamp [UCT]: 2025-07-10 14:45:22 Age [y:d:h:m:s]: 00:174:08:56:20
Block: 1322669 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 123260 RingCT/type: yes/0
Extra: 01bcd2b32ca051b6326152c0062e0d2e2025d50db78cae389b2e8d0a3ad72cb88302110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ba718b75ee6b6e9fbe18791f5d1cb9b2c0e9de1601ecf598ea3639a4334de6d 0.600000000000 1810400 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": 1322679, "vin": [ { "gen": { "height": 1322669 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ba718b75ee6b6e9fbe18791f5d1cb9b2c0e9de1601ecf598ea3639a4334de6d" } } ], "extra": [ 1, 188, 210, 179, 44, 160, 81, 182, 50, 97, 82, 192, 6, 46, 13, 46, 32, 37, 213, 13, 183, 140, 174, 56, 155, 46, 141, 10, 58, 215, 44, 184, 131, 2, 17, 0, 0, 0, 2, 1, 73, 31, 136, 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