Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 967cb35fa7b87ec0ed9d200a0749bc6c2f9b2fbed7202e329ad6470def8ec639

Tx prefix hash: 8b9f0fab9987bbed58cd8e5a04af1a1bdd471da030e9b56744fb5232c99cdc3b
Tx public key: a58789c1dac90dbbafaac5d42f9f1e7d9f7b1775e313360658a59b02ad84d18c
Timestamp: 1697107403 Timestamp [UCT]: 2023-10-12 10:43:23 Age [y:d:h:m:s]: 01:137:10:24:00
Block: 867988 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359209 RingCT/type: yes/0
Extra: 01a58789c1dac90dbbafaac5d42f9f1e7d9f7b1775e313360658a59b02ad84d18c02110000001b75e3f0e9000000000000000000

1 output(s) for total of 0.816573849000 dcy

stealth address amount amount idx
00: 65ddbb6cd01f83c0a69a3c951a07d5ead7e14e70eb0ee08e4174d25366b11e7b 0.816573849000 1322731 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": 867998, "vin": [ { "gen": { "height": 867988 } } ], "vout": [ { "amount": 816573849, "target": { "key": "65ddbb6cd01f83c0a69a3c951a07d5ead7e14e70eb0ee08e4174d25366b11e7b" } } ], "extra": [ 1, 165, 135, 137, 193, 218, 201, 13, 187, 175, 170, 197, 212, 47, 159, 30, 125, 159, 123, 23, 117, 227, 19, 54, 6, 88, 165, 155, 2, 173, 132, 209, 140, 2, 17, 0, 0, 0, 27, 117, 227, 240, 233, 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