Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3737b00088df3d37aa650be019d6a9f0f69fedc27a0059330c30a427d8092dc

Tx prefix hash: 9510def8cc84e8e11b7ba41003016d71accbc26cbd5a2518d8188af4773a78fc
Tx public key: 0af02777c1d034a9cbe04369cc333d21f57bbead5a433d7c7aa67e3f5577e646
Timestamp: 1580976389 Timestamp [UCT]: 2020-02-06 08:06:29 Age [y:d:h:m:s]: 04:330:22:22:45
Block: 59638 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1128048 RingCT/type: yes/0
Extra: 010af02777c1d034a9cbe04369cc333d21f57bbead5a433d7c7aa67e3f5577e646021100000003724f989b000000000000000000

1 output(s) for total of 389.399480643000 dcy

stealth address amount amount idx
00: 472e5ca12cc49bd3e58c924052a3df0043c16bbb285c6d94ed9260c125cd099f 389.399480643000 110093 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": 59648, "vin": [ { "gen": { "height": 59638 } } ], "vout": [ { "amount": 389399480643, "target": { "key": "472e5ca12cc49bd3e58c924052a3df0043c16bbb285c6d94ed9260c125cd099f" } } ], "extra": [ 1, 10, 240, 39, 119, 193, 208, 52, 169, 203, 224, 67, 105, 204, 51, 61, 33, 245, 123, 190, 173, 90, 67, 61, 124, 122, 166, 126, 63, 85, 119, 230, 70, 2, 17, 0, 0, 0, 3, 114, 79, 152, 155, 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