Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bda067f43e290ff7aed3d1be1fb40f7ea3db85625a9d900ca1a22e3861e005e3

Tx prefix hash: e204d3bd3db111ab80de870ef1b7854227b23c21cf90f761b2f10a4e2711c0db
Tx public key: 846e45e06114eb313afbd8c06f56a351674d593cb51542bea0ba31ec73e28a9b
Timestamp: 1755662579 Timestamp [UCT]: 2025-08-20 04:02:59 Age [y:d:h:m:s]: 00:063:13:10:52
Block: 1350327 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 45299 RingCT/type: yes/0
Extra: 01846e45e06114eb313afbd8c06f56a351674d593cb51542bea0ba31ec73e28a9b021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 31fad6232f6877f4f79bc58992e2317bc0f9ed4fab74ecde7bca7adf6d12611e 0.600000000000 1838272 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": 1350337, "vin": [ { "gen": { "height": 1350327 } } ], "vout": [ { "amount": 600000000, "target": { "key": "31fad6232f6877f4f79bc58992e2317bc0f9ed4fab74ecde7bca7adf6d12611e" } } ], "extra": [ 1, 132, 110, 69, 224, 97, 20, 235, 49, 58, 251, 216, 192, 111, 86, 163, 81, 103, 77, 89, 60, 181, 21, 66, 190, 160, 186, 49, 236, 115, 226, 138, 155, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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