Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ff4ba4f1f0561018af4ea5aaa38b68371e6261f814e1b1f3214b9f1e0be4ac5b

Tx prefix hash: a9da67a96ceaaff461175540b1dd2c22bae19e1f5389b6f415dba0a93972f96f
Tx public key: f9a2ead9ba35765f1def21fc9a5bbac1dd34775c4cb206265b17ae3b859566f8
Timestamp: 1733501523 Timestamp [UCT]: 2024-12-06 16:12:03 Age [y:d:h:m:s]: 00:105:19:34:20
Block: 1169386 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75426 RingCT/type: yes/0
Extra: 01f9a2ead9ba35765f1def21fc9a5bbac1dd34775c4cb206265b17ae3b859566f8021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 01d1d9632a416459fbc1e19291092fe82e6024153e8b7dcb8413e2459e5e631d 0.600000000000 1655103 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": 1169396, "vin": [ { "gen": { "height": 1169386 } } ], "vout": [ { "amount": 600000000, "target": { "key": "01d1d9632a416459fbc1e19291092fe82e6024153e8b7dcb8413e2459e5e631d" } } ], "extra": [ 1, 249, 162, 234, 217, 186, 53, 118, 95, 29, 239, 33, 252, 154, 91, 186, 193, 221, 52, 119, 92, 76, 178, 6, 38, 91, 23, 174, 59, 133, 149, 102, 248, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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