Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 662fbf33a6dde37ad1fa2c356e32f387cff51909738be1916af367812e79456f

Tx prefix hash: 0bde77608dd433c6c55d08b8b8f501f9bdc8648b0c514dfd797155bae62357e8
Tx public key: c10ad9ae6dbb4c1bb34a7b7f3c6b497e2239f68d4ae13a95451fa9453d69d94b
Timestamp: 1627507251 Timestamp [UCT]: 2021-07-28 21:20:51 Age [y:d:h:m:s]: 03:102:16:23:40
Block: 302771 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 845786 RingCT/type: yes/0
Extra: 01c10ad9ae6dbb4c1bb34a7b7f3c6b497e2239f68d4ae13a95451fa9453d69d94b0211000000012b68c2f8000000000000000000

1 output(s) for total of 60.924851208000 dcy

stealth address amount amount idx
00: 673f64c4ad699abf2fccddd0343338418b9d80c54eba20723f151cd75e7baf8c 60.924851208000 632100 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": 302781, "vin": [ { "gen": { "height": 302771 } } ], "vout": [ { "amount": 60924851208, "target": { "key": "673f64c4ad699abf2fccddd0343338418b9d80c54eba20723f151cd75e7baf8c" } } ], "extra": [ 1, 193, 10, 217, 174, 109, 187, 76, 27, 179, 74, 123, 127, 60, 107, 73, 126, 34, 57, 246, 141, 74, 225, 58, 149, 69, 31, 169, 69, 61, 105, 217, 75, 2, 17, 0, 0, 0, 1, 43, 104, 194, 248, 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