Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30ecc890da93e233e834a91d49b5817dc388265fb273fe6119874beaf2b05f98

Tx prefix hash: 8f496064f3b15ca1b04f9a0095bb162076505491dc26a7aa29094c0b8a71e81f
Tx public key: 979ffccf0a59f7ef65c26df681c0715dea6dd716a42361c9c74f6d17a3a28d5f
Timestamp: 1725437877 Timestamp [UCT]: 2024-09-04 08:17:57 Age [y:d:h:m:s]: 00:214:02:12:58
Block: 1102639 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 152859 RingCT/type: yes/0
Extra: 01979ffccf0a59f7ef65c26df681c0715dea6dd716a42361c9c74f6d17a3a28d5f02110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 64f666822351c09871d681683513d240f021f0a21da94f431075f4cce7467c37 0.600000000000 1579154 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": 1102649, "vin": [ { "gen": { "height": 1102639 } } ], "vout": [ { "amount": 600000000, "target": { "key": "64f666822351c09871d681683513d240f021f0a21da94f431075f4cce7467c37" } } ], "extra": [ 1, 151, 159, 252, 207, 10, 89, 247, 239, 101, 194, 109, 246, 129, 192, 113, 93, 234, 109, 215, 22, 164, 35, 97, 201, 199, 79, 109, 23, 163, 162, 141, 95, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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