Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 649c5f73f3f9989a4b90ca9d86e961da2cb647c64fe4f107cfe76bc2280d9a1f

Tx prefix hash: 6887e83840a24c4c63647a2e33cb226d4b56bbea397572bc28d4452629b7e5b5
Tx public key: 4e13d275a77c97bd66d9f77c8dc92c8432c3308a55d891466102ec26603006b3
Timestamp: 1695498340 Timestamp [UCT]: 2023-09-23 19:45:40 Age [y:d:h:m:s]: 01:063:15:59:04
Block: 854619 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306760 RingCT/type: yes/0
Extra: 014e13d275a77c97bd66d9f77c8dc92c8432c3308a55d891466102ec26603006b302110000000375e3f0e9000000000000000000

1 output(s) for total of 0.904258362000 dcy

stealth address amount amount idx
00: 9157d382a9b80ebc54ac28e802aa877214a1f68f54cf40c2d704b4dfa89ec4d9 0.904258362000 1308603 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": 854629, "vin": [ { "gen": { "height": 854619 } } ], "vout": [ { "amount": 904258362, "target": { "key": "9157d382a9b80ebc54ac28e802aa877214a1f68f54cf40c2d704b4dfa89ec4d9" } } ], "extra": [ 1, 78, 19, 210, 117, 167, 124, 151, 189, 102, 217, 247, 124, 141, 201, 44, 132, 50, 195, 48, 138, 85, 216, 145, 70, 97, 2, 236, 38, 96, 48, 6, 179, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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