Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae4591c6ef216c97bbb7f73b2c4e89fbaf1e0e9981e03f072c316c82d86756be

Tx prefix hash: 695e346e26e5e35bdcb9612e4c68352aaa3f7a8b37542a24beec43b03a7d92b5
Tx public key: 62c2d215a4fdf0c2bc7233adcf85d28b34eee7755653da03abfe9bd89293570b
Timestamp: 1714680702 Timestamp [UCT]: 2024-05-02 20:11:42 Age [y:d:h:m:s]: 00:360:02:32:01
Block: 1013461 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 257423 RingCT/type: yes/0
Extra: 0162c2d215a4fdf0c2bc7233adcf85d28b34eee7755653da03abfe9bd89293570b0211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d67adc3b630a00bc7d8d3e312caa791973cc356152d2152c94457bf2500587c 0.600000000000 1476284 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": 1013471, "vin": [ { "gen": { "height": 1013461 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d67adc3b630a00bc7d8d3e312caa791973cc356152d2152c94457bf2500587c" } } ], "extra": [ 1, 98, 194, 210, 21, 164, 253, 240, 194, 188, 114, 51, 173, 207, 133, 210, 139, 52, 238, 231, 117, 86, 83, 218, 3, 171, 254, 155, 216, 146, 147, 87, 11, 2, 17, 0, 0, 0, 7, 0, 17, 5, 91, 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