Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b47d384dff1d5f5c8f98717b8f8624567222e5fd24beb4ec65e3d88ccc5a19a6

Tx prefix hash: dc987440ee9170ecc6ee3ed9e1745df31baa0ee37cec67efaafa8436ed886575
Tx public key: 086ae8c337c5fa25c91200b8f110551cd3f21f751cdf9422e2e06dd571932aeb
Timestamp: 1712256362 Timestamp [UCT]: 2024-04-04 18:46:02 Age [y:d:h:m:s]: 01:032:01:27:19
Block: 993341 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 283909 RingCT/type: yes/0
Extra: 01086ae8c337c5fa25c91200b8f110551cd3f21f751cdf9422e2e06dd571932aeb02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d7db6a83c3e03b46d6598a11e75cb908defe2bd41768a29834e6ca2af8a80a1f 0.600000000000 1453727 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": 993351, "vin": [ { "gen": { "height": 993341 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d7db6a83c3e03b46d6598a11e75cb908defe2bd41768a29834e6ca2af8a80a1f" } } ], "extra": [ 1, 8, 106, 232, 195, 55, 197, 250, 37, 201, 18, 0, 184, 241, 16, 85, 28, 211, 242, 31, 117, 28, 223, 148, 34, 226, 224, 109, 213, 113, 147, 42, 235, 2, 17, 0, 0, 0, 3, 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