Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9a814cc21d32e6ef9047693a9a553b58ef68376d396775df68de3c1e0fe1e2d8

Tx prefix hash: 76c4507446a0c50bfca9534d947fa521a8688569e3cba66cefdee8beb1b991f9
Tx public key: 2da1f6c7f5fd40855a285f3fd74a3327741f62047dcc51638d523f853970fea8
Timestamp: 1707681839 Timestamp [UCT]: 2024-02-11 20:03:59 Age [y:d:h:m:s]: 00:361:14:39:49
Block: 955425 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258604 RingCT/type: yes/0
Extra: 012da1f6c7f5fd40855a285f3fd74a3327741f62047dcc51638d523f853970fea802110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 440d452ef13728399265f6a1d60a646b395b0875b736d57c99563bc3b8053c7a 0.600000000000 1414713 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": 955435, "vin": [ { "gen": { "height": 955425 } } ], "vout": [ { "amount": 600000000, "target": { "key": "440d452ef13728399265f6a1d60a646b395b0875b736d57c99563bc3b8053c7a" } } ], "extra": [ 1, 45, 161, 246, 199, 245, 253, 64, 133, 90, 40, 95, 63, 215, 74, 51, 39, 116, 31, 98, 4, 125, 204, 81, 99, 141, 82, 63, 133, 57, 112, 254, 168, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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