Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 581fc2fef880bf4830f21eeeaf7206d212ad13fc01d05f67b3fb0cc16a5f499e

Tx prefix hash: e128e8adb047180d70eb65ab20c105b11482fcdfa6604830ccf2798185da5398
Tx public key: 8112481da3259e7a4259d8a3c9ea7cb657964c0a1cde3999a7849c89e5c089b5
Timestamp: 1712533940 Timestamp [UCT]: 2024-04-07 23:52:20 Age [y:d:h:m:s]: 01:068:12:49:04
Block: 995625 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309911 RingCT/type: yes/0
Extra: 018112481da3259e7a4259d8a3c9ea7cb657964c0a1cde3999a7849c89e5c089b502110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 181711849a50a6df82a5cd612f471e674be02c53926affc994f54ac7ec0017b5 0.600000000000 1456037 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": 995635, "vin": [ { "gen": { "height": 995625 } } ], "vout": [ { "amount": 600000000, "target": { "key": "181711849a50a6df82a5cd612f471e674be02c53926affc994f54ac7ec0017b5" } } ], "extra": [ 1, 129, 18, 72, 29, 163, 37, 158, 122, 66, 89, 216, 163, 201, 234, 124, 182, 87, 150, 76, 10, 28, 222, 57, 153, 167, 132, 156, 137, 229, 192, 137, 181, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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