Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 77c18e98fe4ba8d580f22627041e26588c354b9b1be2b08db348b97e1f96ac26

Tx prefix hash: 9198f81c5eefebb3f5588186fad76c91883effc3b12fa83ce672710ada5ce03b
Tx public key: 01801d9f9c8f2eef04e5979dfc047a3c2b3a7610a2242adfe45169c72674de40
Timestamp: 1707485018 Timestamp [UCT]: 2024-02-09 13:23:38 Age [y:d:h:m:s]: 01:053:23:45:23
Block: 953795 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299629 RingCT/type: yes/0
Extra: 0101801d9f9c8f2eef04e5979dfc047a3c2b3a7610a2242adfe45169c72674de400211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b97bff64bc411a66325940f65b04720813f62709e9f53c4fc74674b964a560ce 0.600000000000 1413051 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": 953805, "vin": [ { "gen": { "height": 953795 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b97bff64bc411a66325940f65b04720813f62709e9f53c4fc74674b964a560ce" } } ], "extra": [ 1, 1, 128, 29, 159, 156, 143, 46, 239, 4, 229, 151, 157, 252, 4, 122, 60, 43, 58, 118, 16, 162, 36, 42, 223, 228, 81, 105, 199, 38, 116, 222, 64, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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