Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 57127f32a06204f66bdc721a95abb490433f8fd7108325cf8c2c0f9f4144abcd

Tx prefix hash: 50db53098661a9a643257b701be87c1b2cb393253f10eaba8cd66cd87b3e167f
Tx public key: 86491c951b58dc34e5ce6bf997ae779dc6a976ef87a67d62d34fcd4ae0c102ea
Timestamp: 1749882189 Timestamp [UCT]: 2025-06-14 06:23:09 Age [y:d:h:m:s]: 00:159:01:55:54
Block: 1304653 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111461 RingCT/type: yes/0
Extra: 0186491c951b58dc34e5ce6bf997ae779dc6a976ef87a67d62d34fcd4ae0c102ea021100000008bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cd03b8bbcf2f9e26645db4a81adf2ca9c7727f9f574d4410cc72cfa0ac9947e3 0.600000000000 1792244 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": 1304663, "vin": [ { "gen": { "height": 1304653 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cd03b8bbcf2f9e26645db4a81adf2ca9c7727f9f574d4410cc72cfa0ac9947e3" } } ], "extra": [ 1, 134, 73, 28, 149, 27, 88, 220, 52, 229, 206, 107, 249, 151, 174, 119, 157, 198, 169, 118, 239, 135, 166, 125, 98, 211, 79, 205, 74, 224, 193, 2, 234, 2, 17, 0, 0, 0, 8, 191, 81, 178, 162, 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