Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a758a328f438f80575af09abaced8a8ea0b20cf4aa036282f8a04056fcbd9254

Tx prefix hash: a972480d3585d01f7abfafc21783cba11b4a4dac887ddbe90a308d6d4abcbf9c
Tx public key: 27e021ca50abdf33e1b6e6e933127d1e813cb27468e385ed8505d09e3aabdb41
Timestamp: 1699027599 Timestamp [UCT]: 2023-11-03 16:06:39 Age [y:d:h:m:s]: 01:217:03:23:43
Block: 883887 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 416235 RingCT/type: yes/0
Extra: 0127e021ca50abdf33e1b6e6e933127d1e813cb27468e385ed8505d09e3aabdb41021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.723294990000 dcy

stealth address amount amount idx
00: 1d764eddc5aad75146816a842d59fb369caa90367ade948372b02e92cccdec6b 0.723294990000 1339610 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": 883897, "vin": [ { "gen": { "height": 883887 } } ], "vout": [ { "amount": 723294990, "target": { "key": "1d764eddc5aad75146816a842d59fb369caa90367ade948372b02e92cccdec6b" } } ], "extra": [ 1, 39, 224, 33, 202, 80, 171, 223, 51, 225, 182, 230, 233, 51, 18, 125, 30, 129, 60, 178, 116, 104, 227, 133, 237, 133, 5, 208, 158, 58, 171, 219, 65, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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