Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20c0f83798be849a4050afafc833d669b03779b57360ecd5c1e8f5a55cf4e524

Tx prefix hash: 536b22d96dd3d76c77c7a1aec39812ef5b2c4dac609f663ac75ae70570ce6b4f
Tx public key: 2e55c4cd88cbcf4ab0194bbb7670334349780bef7c369c1c1ec1ac9d871ddc0f
Timestamp: 1720855691 Timestamp [UCT]: 2024-07-13 07:28:11 Age [y:d:h:m:s]: 00:263:01:31:25
Block: 1064664 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187916 RingCT/type: yes/0
Extra: 012e55c4cd88cbcf4ab0194bbb7670334349780bef7c369c1c1ec1ac9d871ddc0f021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9c2c9cd26d05d09553e1394fcf0688b0e61cc054b431ef7d94837444e67f85af 0.600000000000 1535195 of 15

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": 1064674, "vin": [ { "gen": { "height": 1064664 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9c2c9cd26d05d09553e1394fcf0688b0e61cc054b431ef7d94837444e67f85af" } } ], "extra": [ 1, 46, 85, 196, 205, 136, 203, 207, 74, 176, 25, 75, 187, 118, 112, 51, 67, 73, 120, 11, 239, 124, 54, 156, 28, 30, 193, 172, 157, 135, 29, 220, 15, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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