Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ffc4796a57f6062d541d8a1bfd745ad0ebe266d9c1806acb31bd32455ff64a6

Tx prefix hash: 01db624e968453d6fc273df981ebf9c31f11e19b81e1997b18aaa165049a9024
Tx public key: d2b15338e2d4f99c4502282223a64da51a71e26dbd596a2d14e8c9249efb4185
Timestamp: 1738020226 Timestamp [UCT]: 2025-01-27 23:23:46 Age [y:d:h:m:s]: 00:144:07:15:58
Block: 1206550 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103023 RingCT/type: yes/0
Extra: 01d2b15338e2d4f99c4502282223a64da51a71e26dbd596a2d14e8c9249efb41850211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 841bc9e1bc1e72dc94edff2582e8e48a26c5498ee175efe9e364b89dcde345ec 0.600000000000 1693259 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": 1206560, "vin": [ { "gen": { "height": 1206550 } } ], "vout": [ { "amount": 600000000, "target": { "key": "841bc9e1bc1e72dc94edff2582e8e48a26c5498ee175efe9e364b89dcde345ec" } } ], "extra": [ 1, 210, 177, 83, 56, 226, 212, 249, 156, 69, 2, 40, 34, 35, 166, 77, 165, 26, 113, 226, 109, 189, 89, 106, 45, 20, 232, 201, 36, 158, 251, 65, 133, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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