Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c10de5ad238b56a1fa97e4ede06a5901da47a2a0ec9316681cdcfc484cfc2f98

Tx prefix hash: 2dcbbb4708036e5b259dcaf99b90c9f9a7c1c0214ee5d1c95ef256c278e4a5b5
Tx public key: 0ba3ad0388024b6fad4860f8b4e54c85d24a82dc8bddca5b32229fcc8f1aba46
Timestamp: 1643892917 Timestamp [UCT]: 2022-02-03 12:55:17 Age [y:d:h:m:s]: 02:298:20:40:14
Block: 431347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 732123 RingCT/type: yes/0
Extra: 010ba3ad0388024b6fad4860f8b4e54c85d24a82dc8bddca5b32229fcc8f1aba46021100000002c9067537000000000000000000

1 output(s) for total of 22.843815003000 dcy

stealth address amount amount idx
00: 25c7c8c2d8b0b33bd8188307325b8173bc301318dd5b2d096fdc4e64cb8311a6 22.843815003000 841523 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": 431357, "vin": [ { "gen": { "height": 431347 } } ], "vout": [ { "amount": 22843815003, "target": { "key": "25c7c8c2d8b0b33bd8188307325b8173bc301318dd5b2d096fdc4e64cb8311a6" } } ], "extra": [ 1, 11, 163, 173, 3, 136, 2, 75, 111, 173, 72, 96, 248, 180, 229, 76, 133, 210, 74, 130, 220, 139, 221, 202, 91, 50, 34, 159, 204, 143, 26, 186, 70, 2, 17, 0, 0, 0, 2, 201, 6, 117, 55, 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