Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5bd3e94b21530dbec1472fc9699d9b4dea6dd4caf3b47b027f3c19067c7b9b8

Tx prefix hash: 20780d36299d516ece6c7b205de1f2f90710cc9d6d0807acc06cd97b17617105
Tx public key: 66c0d30709a7bb1f1cace211fdffbddeadc032241e293ffbb37bf47ea7884525
Timestamp: 1675628425 Timestamp [UCT]: 2023-02-05 20:20:25 Age [y:d:h:m:s]: 01:287:11:51:42
Block: 690579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 466408 RingCT/type: yes/0
Extra: 0166c0d30709a7bb1f1cace211fdffbddeadc032241e293ffbb37bf47ea7884525021100000002e7ace25d000000000000000000

1 output(s) for total of 3.161003867000 dcy

stealth address amount amount idx
00: 9660b1375eca43b869b1eda082f97538bce02ca2e2f65ed8d76dd996f33b0a4f 3.161003867000 1133309 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": 690589, "vin": [ { "gen": { "height": 690579 } } ], "vout": [ { "amount": 3161003867, "target": { "key": "9660b1375eca43b869b1eda082f97538bce02ca2e2f65ed8d76dd996f33b0a4f" } } ], "extra": [ 1, 102, 192, 211, 7, 9, 167, 187, 31, 28, 172, 226, 17, 253, 255, 189, 222, 173, 192, 50, 36, 30, 41, 63, 251, 179, 123, 244, 126, 167, 136, 69, 37, 2, 17, 0, 0, 0, 2, 231, 172, 226, 93, 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