Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85cb2df95078292ee74fe01f8912b7636160be4631d23b891d68586f6319235c

Tx prefix hash: d6f6256c68964b48efbef24d581b9713aba1114833ba02c9231c07b3532b0a91
Tx public key: 08afbc64a26257babe5aab1e6515b2f9e9e98bbf9ab377c464e28a1b6a2823bf
Timestamp: 1698450751 Timestamp [UCT]: 2023-10-27 23:52:31 Age [y:d:h:m:s]: 02:022:20:51:13
Block: 879117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 535934 RingCT/type: yes/0
Extra: 0108afbc64a26257babe5aab1e6515b2f9e9e98bbf9ab377c464e28a1b6a2823bf0211000000014b8f5122000000000000000000

1 output(s) for total of 0.750102226000 dcy

stealth address amount amount idx
00: 9b47e82108c3e17d13bd905731c62d448d0914d36c3aca0caa257adc0d56d982 0.750102226000 1334619 of 0

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": 879127, "vin": [ { "gen": { "height": 879117 } } ], "vout": [ { "amount": 750102226, "target": { "key": "9b47e82108c3e17d13bd905731c62d448d0914d36c3aca0caa257adc0d56d982" } } ], "extra": [ 1, 8, 175, 188, 100, 162, 98, 87, 186, 190, 90, 171, 30, 101, 21, 178, 249, 233, 233, 139, 191, 154, 179, 119, 196, 100, 226, 138, 27, 106, 40, 35, 191, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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