Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8063948dd056dcb7e58c271cc1d958779d11ae51135b29fe41c3ca6a16653d51

Tx prefix hash: 96fbd233d3f020c6111a651208a8f67536eb12f840378dc0aaea017e60463a0e
Tx public key: 50190c62e8e9e5881c523b28f45d2e3a3d5465f7e4907f5dcb988cea13c72926
Timestamp: 1717713318 Timestamp [UCT]: 2024-06-06 22:35:18 Age [y:d:h:m:s]: 01:177:21:53:35
Block: 1038601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 385754 RingCT/type: yes/0
Extra: 0150190c62e8e9e5881c523b28f45d2e3a3d5465f7e4907f5dcb988cea13c72926021100000001d749f511000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9c59b5aa0bfb1f3b325991ecce1cb1e0916a265d7a15d16ba38207e55bc7b8d8 0.600000000000 1507162 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": 1038611, "vin": [ { "gen": { "height": 1038601 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c59b5aa0bfb1f3b325991ecce1cb1e0916a265d7a15d16ba38207e55bc7b8d8" } } ], "extra": [ 1, 80, 25, 12, 98, 232, 233, 229, 136, 28, 82, 59, 40, 244, 93, 46, 58, 61, 84, 101, 247, 228, 144, 127, 93, 203, 152, 140, 234, 19, 199, 41, 38, 2, 17, 0, 0, 0, 1, 215, 73, 245, 17, 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