Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 043ce04de869c2727b9e6ff29224b694c772e697b90fe86b0d7616d29063bd28

Tx prefix hash: 4c0611fa251661e408a701ec11115392ed64b872854763cc07396464e9a83e36
Tx public key: cc115ada85e07d530933bf45f22c404a2b64cad1aea20168e8e5a58138f6a7bf
Timestamp: 1582292723 Timestamp [UCT]: 2020-02-21 13:45:23 Age [y:d:h:m:s]: 04:281:18:39:45
Block: 69530 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1093895 RingCT/type: yes/0
Extra: 01cc115ada85e07d530933bf45f22c404a2b64cad1aea20168e8e5a58138f6a7bf021100000001724f989b000000000000000000

1 output(s) for total of 361.092984732000 dcy

stealth address amount amount idx
00: 1070b6c6c2d274c5880d1355d98c2c213df964489d620b8c54dc1838ff4f413b 361.092984732000 128250 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": 69540, "vin": [ { "gen": { "height": 69530 } } ], "vout": [ { "amount": 361092984732, "target": { "key": "1070b6c6c2d274c5880d1355d98c2c213df964489d620b8c54dc1838ff4f413b" } } ], "extra": [ 1, 204, 17, 90, 218, 133, 224, 125, 83, 9, 51, 191, 69, 242, 44, 64, 74, 43, 100, 202, 209, 174, 162, 1, 104, 232, 229, 165, 129, 56, 246, 167, 191, 2, 17, 0, 0, 0, 1, 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