Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 840b29f7ef0e441448153e422d3f177ffc46e23bbbeaed78c0ece7d2540b30a8

Tx prefix hash: ec9ea69ec9df07aa64a85be7bec56d1d12be9c44828fad303dd6fc57b78e373e
Tx public key: 5a19b3b718d47f6fae8a8290da0624d3183aba29ee7cdcef5f9a8667bfa9e3ec
Timestamp: 1764566849 Timestamp [UCT]: 2025-12-01 05:27:29 Age [y:d:h:m:s]: 00:004:03:33:52
Block: 1423910 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 2980 RingCT/type: yes/0
Extra: 015a19b3b718d47f6fae8a8290da0624d3183aba29ee7cdcef5f9a8667bfa9e3ec02110000000570609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a548121dbe187f0f700edc0a76b06bacb7ae76a9895a24c943d5ddcb59e3317d 0.600000000000 1912537 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": 1423920, "vin": [ { "gen": { "height": 1423910 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a548121dbe187f0f700edc0a76b06bacb7ae76a9895a24c943d5ddcb59e3317d" } } ], "extra": [ 1, 90, 25, 179, 183, 24, 212, 127, 111, 174, 138, 130, 144, 218, 6, 36, 211, 24, 58, 186, 41, 238, 124, 220, 239, 95, 154, 134, 103, 191, 169, 227, 236, 2, 17, 0, 0, 0, 5, 112, 96, 157, 3, 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