Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f7cb676142e53442d4bdfb907b697fd50d6d74f4a92e16189deab7f02bead24

Tx prefix hash: 30c14dd32c07b8d640b8624e1304a1b0935005ed2c8c5074d088183c96843ab9
Tx public key: f9f918b4d7e2d56a928014bb9fdca290853364dde379e6fbe96479a42be8894a
Timestamp: 1674888023 Timestamp [UCT]: 2023-01-28 06:40:23 Age [y:d:h:m:s]: 02:027:07:34:52
Block: 684423 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 541123 RingCT/type: yes/0
Extra: 01f9f918b4d7e2d56a928014bb9fdca290853364dde379e6fbe96479a42be8894a0211000000015029cbac000000000000000000

1 output(s) for total of 3.313007504000 dcy

stealth address amount amount idx
00: ed1cce0117add3ad39cd9a0c680833ce8b997c9a0a1d4aea3606b411c71d27d5 3.313007504000 1126654 of 0

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": 684433, "vin": [ { "gen": { "height": 684423 } } ], "vout": [ { "amount": 3313007504, "target": { "key": "ed1cce0117add3ad39cd9a0c680833ce8b997c9a0a1d4aea3606b411c71d27d5" } } ], "extra": [ 1, 249, 249, 24, 180, 215, 226, 213, 106, 146, 128, 20, 187, 159, 220, 162, 144, 133, 51, 100, 221, 227, 121, 230, 251, 233, 100, 121, 164, 43, 232, 137, 74, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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