Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b64bd6b7baf9d821d51ced84da59b792dafb2617dc30f6692c69b48103510b5a

Tx prefix hash: d107b2009c43b5c5ac8d3ad10f60facdf64b7a72a5d29a5741812984045775bf
Tx public key: 0c3017780391dbc21f5f07911b53b08538fa3c975435a50c64e4a95a1f05101a
Timestamp: 1732297245 Timestamp [UCT]: 2024-11-22 17:40:45 Age [y:d:h:m:s]: 00:133:18:13:51
Block: 1159410 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95423 RingCT/type: yes/0
Extra: 010c3017780391dbc21f5f07911b53b08538fa3c975435a50c64e4a95a1f05101a021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d8546c0f456cdd0c7fdf4795a2ffa5ac4e62451d0acef8d03c1d00f263713f4 0.600000000000 1645045 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": 1159420, "vin": [ { "gen": { "height": 1159410 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d8546c0f456cdd0c7fdf4795a2ffa5ac4e62451d0acef8d03c1d00f263713f4" } } ], "extra": [ 1, 12, 48, 23, 120, 3, 145, 219, 194, 31, 95, 7, 145, 27, 83, 176, 133, 56, 250, 60, 151, 84, 53, 165, 12, 100, 228, 169, 90, 31, 5, 16, 26, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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