Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c72eb939526fc826e7105df2aed357a15718a10c60737f7288d6655516caf394

Tx prefix hash: 61fa5542ca62e3b00724a31a1c08190821c8dd4cc0da7dcdbdc1d26294d95625
Tx public key: d62fb217c7df45e51f2530f15b37d3469db5c70a900d7be953965afe3bdaa615
Timestamp: 1721840965 Timestamp [UCT]: 2024-07-24 17:09:25 Age [y:d:h:m:s]: 00:267:17:03:44
Block: 1072809 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 191265 RingCT/type: yes/0
Extra: 01d62fb217c7df45e51f2530f15b37d3469db5c70a900d7be953965afe3bdaa61502110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4ed5e78f3fcac94ac8462d76cc0f18390312439a6869f5e6def8957b07c873f 0.600000000000 1545306 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": 1072819, "vin": [ { "gen": { "height": 1072809 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4ed5e78f3fcac94ac8462d76cc0f18390312439a6869f5e6def8957b07c873f" } } ], "extra": [ 1, 214, 47, 178, 23, 199, 223, 69, 229, 31, 37, 48, 241, 91, 55, 211, 70, 157, 181, 199, 10, 144, 13, 123, 233, 83, 150, 90, 254, 59, 218, 166, 21, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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