Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9461374422142a8e362829be8af0ae84c3fea13718a7c128ccbb4f6bd9d08427

Tx prefix hash: 3a422b485df658fd47702fa9f06788d62b6595dad57f712a209c31d4970c92d9
Tx public key: 9f55d770e27021172b166e1b98d4a1e151f5df378c48c485e520b27e8ff3b3a5
Timestamp: 1706657483 Timestamp [UCT]: 2024-01-30 23:31:23 Age [y:d:h:m:s]: 01:084:18:56:29
Block: 946922 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321685 RingCT/type: yes/0
Extra: 019f55d770e27021172b166e1b98d4a1e151f5df378c48c485e520b27e8ff3b3a502110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f08eb7abe4373c201216ba45f89525aa0b0c5cf4f76a438686c88c31f5e5b5ff 0.600000000000 1405268 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": 946932, "vin": [ { "gen": { "height": 946922 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f08eb7abe4373c201216ba45f89525aa0b0c5cf4f76a438686c88c31f5e5b5ff" } } ], "extra": [ 1, 159, 85, 215, 112, 226, 112, 33, 23, 43, 22, 110, 27, 152, 212, 161, 225, 81, 245, 223, 55, 140, 72, 196, 133, 229, 32, 178, 126, 143, 243, 179, 165, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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