Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0c4814a60da84280b8c2ee58b4731f67759dd59e498e9898f9766a1f63b5be32

Tx prefix hash: 83226a76a5648bd7065423c3ed2879c45e505b02fff1f26237804c00f2d72cf5
Tx public key: 05e4fe6749abd1cf6ad3d5f0ff7e537b25b980235f9c1c097abd4a137e445353
Timestamp: 1759018997 Timestamp [UCT]: 2025-09-28 00:23:17 Age [y:d:h:m:s]: 00:054:01:38:15
Block: 1377919 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 38712 RingCT/type: yes/0
Extra: 0105e4fe6749abd1cf6ad3d5f0ff7e537b25b980235f9c1c097abd4a137e445353021100000002a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a31ffc544f7099e5662da5b925b876d8a134f6246c3068155df0ec21cb06e762 0.600000000000 1866014 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": 1377929, "vin": [ { "gen": { "height": 1377919 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a31ffc544f7099e5662da5b925b876d8a134f6246c3068155df0ec21cb06e762" } } ], "extra": [ 1, 5, 228, 254, 103, 73, 171, 209, 207, 106, 211, 213, 240, 255, 126, 83, 123, 37, 185, 128, 35, 95, 156, 28, 9, 122, 189, 74, 19, 126, 68, 83, 83, 2, 17, 0, 0, 0, 2, 165, 220, 205, 121, 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