Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c440f8711bc3472ae6d4e83e29bce4419378a38345221d5621fbbddccd93b2e

Tx prefix hash: 97193e49e87a320934e4e2a7a0829507f49200457c974d0432b712d1b8b5d4d7
Tx public key: a1160394e5af4241f94bed13f282d3bede123f008573723bbd4da501f5e2fc07
Timestamp: 1713857940 Timestamp [UCT]: 2024-04-23 07:39:00 Age [y:d:h:m:s]: 00:309:07:25:07
Block: 1006637 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 221091 RingCT/type: yes/0
Extra: 01a1160394e5af4241f94bed13f282d3bede123f008573723bbd4da501f5e2fc070211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2067dea5b6f8ea15bb5894ffe72601846bea455feb2a0f9c94a40984cbe4adb 0.600000000000 1467723 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": 1006647, "vin": [ { "gen": { "height": 1006637 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2067dea5b6f8ea15bb5894ffe72601846bea455feb2a0f9c94a40984cbe4adb" } } ], "extra": [ 1, 161, 22, 3, 148, 229, 175, 66, 65, 249, 75, 237, 19, 242, 130, 211, 190, 222, 18, 63, 0, 133, 115, 114, 59, 189, 77, 165, 1, 245, 226, 252, 7, 2, 17, 0, 0, 0, 3, 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