Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69f6ca4cc7a5658dca8eacea1c824d1a6ccfeae81cec76b336817052dc3abb98

Tx prefix hash: 165776ed6fa19604ce2c6d35881a45ecc64b345140274302fc20b91cf8a9cd1a
Tx public key: 264feefcb9f8011c8a5cb8b6ec87d4834934f9b463018855d26c89b1fae41010
Timestamp: 1722102481 Timestamp [UCT]: 2024-07-27 17:48:01 Age [y:d:h:m:s]: 00:238:10:43:48
Block: 1074985 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 170329 RingCT/type: yes/0
Extra: 01264feefcb9f8011c8a5cb8b6ec87d4834934f9b463018855d26c89b1fae4101002110000001fe914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 90e0219472b9c23c9fcae3eacfca32d7023bc7e2b5bb80319953d219f48ac16a 0.600000000000 1547504 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": 1074995, "vin": [ { "gen": { "height": 1074985 } } ], "vout": [ { "amount": 600000000, "target": { "key": "90e0219472b9c23c9fcae3eacfca32d7023bc7e2b5bb80319953d219f48ac16a" } } ], "extra": [ 1, 38, 79, 238, 252, 185, 248, 1, 28, 138, 92, 184, 182, 236, 135, 212, 131, 73, 52, 249, 180, 99, 1, 136, 85, 210, 108, 137, 177, 250, 228, 16, 16, 2, 17, 0, 0, 0, 31, 233, 20, 221, 21, 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