Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6618b93cfa328d639911cb2f34cd46b5e2b447879d9644d1fac3c389cfb5fef9

Tx prefix hash: 863c8bfc4447d551c2f738945394fbb4afcb02bde2b0f77952625fcc2dacda73
Tx public key: e5461804b3fda949b3d51e06ad3a3e3a335449376c3021daafe4860ec7e8783e
Timestamp: 1672797110 Timestamp [UCT]: 2023-01-04 01:51:50 Age [y:d:h:m:s]: 01:333:18:54:07
Block: 667091 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 499583 RingCT/type: yes/0
Extra: 01e5461804b3fda949b3d51e06ad3a3e3a335449376c3021daafe4860ec7e8783e02110000000333af99f4000000000000000000

1 output(s) for total of 3.781382029000 dcy

stealth address amount amount idx
00: 71fcf7ced4e21b68d34880bcf0e02f0d1c354eacea393ad873994407d117bf9c 3.781382029000 1108256 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": 667101, "vin": [ { "gen": { "height": 667091 } } ], "vout": [ { "amount": 3781382029, "target": { "key": "71fcf7ced4e21b68d34880bcf0e02f0d1c354eacea393ad873994407d117bf9c" } } ], "extra": [ 1, 229, 70, 24, 4, 179, 253, 169, 73, 179, 213, 30, 6, 173, 58, 62, 58, 51, 84, 73, 55, 108, 48, 33, 218, 175, 228, 134, 14, 199, 232, 120, 62, 2, 17, 0, 0, 0, 3, 51, 175, 153, 244, 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