Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6658f3cf2e9080ef988aa4681dd186cc4b899499748d3c417a3bcc7804d6d4d

Tx prefix hash: 28654bc8c839d7ac8bb19e818a018509d682d1e46539083bd28041a7132f323b
Tx public key: e588483253ab0d97c9d9b3b290cc237e8d732ffd2afb5a0db7b16f4d52650cc2
Timestamp: 1694939204 Timestamp [UCT]: 2023-09-17 08:26:44 Age [y:d:h:m:s]: 01:268:12:21:17
Block: 849980 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 453018 RingCT/type: yes/0
Extra: 01e588483253ab0d97c9d9b3b290cc237e8d732ffd2afb5a0db7b16f4d52650cc2021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.936835789000 dcy

stealth address amount amount idx
00: 053a09f044c5b64d98ed0d88c93f61f33e96e7f2eaac482d743fdacb5ab7240b 0.936835789000 1303672 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": 849990, "vin": [ { "gen": { "height": 849980 } } ], "vout": [ { "amount": 936835789, "target": { "key": "053a09f044c5b64d98ed0d88c93f61f33e96e7f2eaac482d743fdacb5ab7240b" } } ], "extra": [ 1, 229, 136, 72, 50, 83, 171, 13, 151, 201, 217, 179, 178, 144, 204, 35, 126, 141, 115, 47, 253, 42, 251, 90, 13, 183, 177, 111, 77, 82, 101, 12, 194, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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