Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b7b289584ff7028cf88fe58c4570dcd85cfe8676cc6d09f30e218d2c06667cb

Tx prefix hash: 85bd277008e0239adece08ad76d2f197147c2f2f2a7f4fef3530188b7bb44ec6
Tx public key: dac707b34a4a474d458e82e8e67b7b2160d4964e79cd0b58fd918c5435c8e031
Timestamp: 1722068703 Timestamp [UCT]: 2024-07-27 08:25:03 Age [y:d:h:m:s]: 01:110:00:25:27
Block: 1074696 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 337143 RingCT/type: yes/0
Extra: 01dac707b34a4a474d458e82e8e67b7b2160d4964e79cd0b58fd918c5435c8e031021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 37a9c5079dd7af2539325d1a4ae2359e815272477f1eb7572d9188616a345d12 0.600000000000 1547213 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": 1074706, "vin": [ { "gen": { "height": 1074696 } } ], "vout": [ { "amount": 600000000, "target": { "key": "37a9c5079dd7af2539325d1a4ae2359e815272477f1eb7572d9188616a345d12" } } ], "extra": [ 1, 218, 199, 7, 179, 74, 74, 71, 77, 69, 142, 130, 232, 230, 123, 123, 33, 96, 212, 150, 78, 121, 205, 11, 88, 253, 145, 140, 84, 53, 200, 224, 49, 2, 17, 0, 0, 0, 1, 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