Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a7df7f9b5e19b55a5a3160b913a0ed74e82d60fefb150f547b55575a97b6655

Tx prefix hash: b600b48e1f1dd6be83d23648d626c99c672863d5be494e01c396937c8ccd3b51
Tx public key: b9a19334e3095cf9436dca3a67cae908cb18507936c77de23918e54b70f05503
Timestamp: 1726419341 Timestamp [UCT]: 2024-09-15 16:55:41 Age [y:d:h:m:s]: 00:058:20:48:37
Block: 1110774 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 42085 RingCT/type: yes/0
Extra: 01b9a19334e3095cf9436dca3a67cae908cb18507936c77de23918e54b70f0550302110000000be914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c5f2da28719bd6943e6c52434cb115e37c6e1e10b2588a077b985dd53b0c1b03 0.600000000000 1589501 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": 1110784, "vin": [ { "gen": { "height": 1110774 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c5f2da28719bd6943e6c52434cb115e37c6e1e10b2588a077b985dd53b0c1b03" } } ], "extra": [ 1, 185, 161, 147, 52, 227, 9, 92, 249, 67, 109, 202, 58, 103, 202, 233, 8, 203, 24, 80, 121, 54, 199, 125, 226, 57, 24, 229, 75, 112, 240, 85, 3, 2, 17, 0, 0, 0, 11, 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