Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 06987412c35aab5d551a1e9400043a6a65ffe2912a69f22b54019d52e9a6858a

Tx prefix hash: 9313bd927249a1f814495aabd8b5aac4ba76282ff3061371dcc9882df43112d2
Tx public key: 997a87e077ba74e0c651717d509c4fa146a6c88f98179e9751cd9e84e5b97af1
Timestamp: 1715166697 Timestamp [UCT]: 2024-05-08 11:11:37 Age [y:d:h:m:s]: 00:331:08:53:20
Block: 1017503 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236840 RingCT/type: yes/0
Extra: 01997a87e077ba74e0c651717d509c4fa146a6c88f98179e9751cd9e84e5b97af10211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c11d0a5ef3d2fc7d2980b1d37fa45a7beeec6a47331b593dd1dfa2b153eb978 0.600000000000 1481286 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": 1017513, "vin": [ { "gen": { "height": 1017503 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c11d0a5ef3d2fc7d2980b1d37fa45a7beeec6a47331b593dd1dfa2b153eb978" } } ], "extra": [ 1, 153, 122, 135, 224, 119, 186, 116, 224, 198, 81, 113, 125, 80, 156, 79, 161, 70, 166, 200, 143, 152, 23, 158, 151, 81, 205, 158, 132, 229, 185, 122, 241, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 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